> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/administration-and-configuration/managing-and-customizing-the-home-page/saving-and-publishing-the-home-page.md).

# Saving & Publishing the Home Page

Save your work as a draft or publish the Home Page for all environment users.

Administrators can either save their changes as a private draft or publish the Home Page to make it live for all users in the environment.

***

## Managing Changes in the Editor

The following options provide a structured way to manage your Home Page revisions:

{% stepper %}
{% step %}

### Saving Changes

Click **Save Changes** in the top bar to save your Home Page design as a private draft. This allows you to edit it across multiple sessions without publishing it to the environment. 

{% hint style="info" %}
Drafts are visible only to the administrator who created them and remain intact even after exiting the **Editor**.
{% endhint %}

#### <i class="fa-floppy-disk">:floppy-disk:</i>  What Happens After Saving

* The draft is stored in the **Editor** as your personal version of the Home Page.
* Each additional save updates this draft.
* The live Home Page remains unchanged.

#### <i class="fa-pen-to-square">:pen-to-square:</i>  When You Reopen the Editor

* The draft loads automatically.
* You may continue editing or discard the draft to revert to the last published version—the current environment home page.
  * If no published version exists, the draft remains the only available version.

{% hint style="info" %}
This approach enables administrators to make incremental updates without impacting users, helping prevent accidental overwrites and ensuring changes are published only when finalized.
{% endhint %}

***

{% endstep %}

{% step %}

### Discarding Changes

Click **Revert Changes** in the top bar to discard all unsaved changes, returning to the last published version.

***

{% endstep %}

{% step %}

### Publishing Changes

When ready, click **Publish** in the top bar to publish your draft.

{% hint style="warning" %}
If another administrator has unpublished changes, a warning appears to help prevent conflicting updates.
{% endhint %}

#### <i class="fa-paper-plane">:paper-plane:</i>  What Happens After Publishing

* The draft becomes the new live Home Page, visible to all environment users.
* Admins will see the updated Home Page in **View Mode**, not as an editable draft.

***

{% endstep %}
{% endstepper %}

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/administration-and-configuration/managing-and-customizing-the-home-page/saving-and-publishing-the-home-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.