> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serviceplan-agents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Preview and going live

> How to review the preview, reject or approve it, and what happens when it goes live.

> [!NOTE]
>
> **In short:** Every request first produces a preview. It is not public. An existing live dashboard remains unchanged while you review. Only when you click **Approve and put live** do your readers see the new version.

## The preview

As soon as the preview is ready, the **Builds** page shows **Ready for you** on your request. There you will find these buttons:

| Button | What it does |
| - | - |
| **Open preview** | Opens the preview in a new tab. |
| **Copy review link** | Copies a link to the preview. Use it to show the preview to colleagues. |
| **Approve and put live** | Turns the preview into the dashboard under the fixed link. |
| **Reject** | Rejects the preview. Your reasoning goes to Alex as the next job. |

> [!NOTE]
>
> **Screenshot needed:** a request on the Builds page with "Ready for you" and the four buttons.

### Sample figures

If no real data is available yet, the preview shows **sample figures** instead of empty boxes. This lets you assess the layout and charts anyway. As long as an area contains sample figures, a notice appears at the top of the dashboard, such as *"Some figures on this dashboard are placeholders."* It disappears once all affected areas have received real data. Sample figures are never carried over.

### The display check

When you click **Approve and put live**, the dashboard is first opened the way readers see it. If a section stays empty despite available data, or the page shows an error, **the dashboard is not published**. You then receive a clear explanation and the recommendation to request a revision.

## Rejecting

Click **Reject** and describe as specifically as possible what should change. Alex uses your reasoning as the next job.

* **New dashboard or copy** (nothing is live yet): With **Order another round**, Alex rebuilds the dashboard based on the same job. He fixes the points you raised. Each revision costs credits again. With **Discard**, you throw away the preview.
* **Change to a live dashboard:** Request the next revision via **Ask for a change**. The live dashboard is not affected.

## Going live

**Approve and put live** does three things:

**1. The fixed link shows the new version**

The preview becomes the dashboard under the **fixed link**. A change goes live under the same link, without interruption.

**2. The refreshes start**

On the first go-live, the Console starts the **automatic refreshes**. They run through your account. Each data area is refreshed according to its defined cadence. Every refresh consumes credits. The Console points this out in advance.

**3. Proposals arrive by email**

From the first go-live onward, the person responsible (owner) receives an email whenever coworkers propose changes to the rules. See [Rules, method and lists](https://docs.serviceplan-agents.com/en/live-apps/feed-guides.md).

**What your readers see:** From the first go-live onward, the dashboard can be reached via the fixed link. If you have set a password, it must be entered first. Later changes become visible automatically under the same link as soon as you approve them. How to share the link and password is explained under [Access: link and password](https://docs.serviceplan-agents.com/en/live-apps/password-and-sharing.md).

## Changes to a live dashboard

When you request a change, the live dashboard keeps running the whole time. Your readers see the old version until you approve the new one. Then the same link switches over without interruption.

```mermaid theme={"dark"}
%%{init: {'theme':'base', 'themeVariables': {'primaryColor':'#FFF5F5','primaryBorderColor':'#FF4B4F','primaryTextColor':'#141414','lineColor':'#FF4B4F','tertiaryColor':'#ffffff','fontSize':'14px'}}}%%
flowchart LR
    L["Live version<br/>keeps running"] --> S["Readers still see<br/>the old version"]
    P["Alex builds the change<br/>as a preview"] --> A["You approve"]
    A --> N["The same link shows<br/>the new version"]
```

> [!TIP]
>
> An approved change turns out not to fit? Then return to the previous version of the dashboard. Normally, you use **Roll back to before this** on the newest version in the **History** tab. If that isn't available, the **Access** tab shows **Roll back to previous version** instead. The link stays the same.

## What you can do next

> [card] [Data areas and refreshes](https://docs.serviceplan-agents.com/en/live-apps/data-feeds.md)
>
> What keeps the figures up to date.

> [card] [Access: link and password](https://docs.serviceplan-agents.com/en/live-apps/password-and-sharing.md)
>
> Give your team access.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.