> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/administration/landing-pages.md).

# Prepare landing pages

Prepare the page a person sees when they open YouDesign Command, such as a financial page for your CFO, from Global Settings or from the assistant.

{% hint style="info" %}
You need the **Command Admin** role.
{% endhint %}

A landing page is what a person sees when they open Command. You can prepare one for someone, such as a financial page for your CFO. They see it until they make their own page, which starts as a copy of yours.

## Open Landing pages

1. Click **Open menu** (☰) in the header and expand **Global Settings**.
2. Choose **Landing pages**.

Below the search box, each person you have prepared a page for is listed with when their page was last saved, and **Edit page** and **Remove**.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-d489f3dbab23f6780470e2e08687bbf82f2ac227%2Fcommand-settings-landing-pages.png?alt=media" alt="The Landing pages section of Global Settings, with the Prepare a page for search box and one prepared page with Edit page and Remove."><figcaption><p>Global Settings, Landing pages</p></figcaption></figure>

## How to

### Prepare a page

1. In **Prepare a page for…**, search for the person by name or email and pick them.
2. The page opens in edit mode, titled *Landing page for* , starting from the default Home sections.
3. Arrange it like any [dashboard](https://docs.ins-pi.com/command/features/dashboards.md). Changes are saved as you make them.
4. Click **Close** when you are done.

To start from something you already have, use **Start from another landing page or a dashboard…** and confirm with **Replace page**. The page becomes a copy: later changes to the original do not reach it.

### Prepare a page from the assistant

Ask the Command Dialog, for example *Prepare a landing page for Jane Smith from the dashboard CFO Overview*. Check the proposal and click **Prepare page**.

### Remove a page

Click **Remove** next to the person. The page moves to the trash, and the person sees their own Home or the default page again.

## Good to know

* **Share what the page shows.** Tiles and embedded content open only what the person can see, so share that content with them too. The **My work** widgets show their own tasks and records, not yours.
* **Saving shows your page again.** If the person has made their own page, your next save brings yours back, and Command tells them their own page is still in My Space.
* The person receives the page as a viewer. Their first **Edit** makes their own copy, and yours stays unchanged.
* If two administrators edit the same page, Command never overwrites the newer change; it shows the newer page instead.

## Related

* [Home and landing pages](https://docs.ins-pi.com/command/the-portal/home.md)
* [Global Settings](https://docs.ins-pi.com/command/administration/global-settings.md)
* [Dashboards](https://docs.ins-pi.com/command/features/dashboards.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ins-pi.com/command/administration/landing-pages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
