> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/basics/dashboards-new-experience/create-a-dashboard-new-experience.md).

# Create a dashboard (new experience)

{% hint style="info" %}
You are viewing documentation for the new dashboards experience.
{% endhint %}

{% embed url="<https://phocassoftware.wistia.com/s/654papm7zl1k3sl>" %}
Create a dashboard
{% endembed %}

You can start creating a dashboard from several places in Phocas.

#### On your Phocas homepage

<figure><img src="https://900295827-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7pj8v25BOyqZTdG5mdD1%2Fuploads%2Fgit-blob-cf1161893007e0b1b2f6ad2b0c2f96aa1fc73e69%2Fimage%20(675).png?alt=media" alt=""><figcaption></figcaption></figure>

1. Click the **Dashboards** tab, then click **Create dashboard**
2. Select **New experience (beta)**

<div align="left"><figure><img src="https://900295827-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7pj8v25BOyqZTdG5mdD1%2Fuploads%2Fgit-blob-08c76fbd6b8dce2c54019d130754e05d7e3f937f%2Fimage%20(735).png?alt=media" alt="" width="270"><figcaption></figcaption></figure></div>

#### In the navigation menu

click **Dashboards**, then do one of the following:q

* Click **Create dashboard** in the blue banner at the bottom of the panel.

<div align="left"><figure><img src="https://900295827-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7pj8v25BOyqZTdG5mdD1%2Fuploads%2Fgit-blob-18651404cde6d0c1c9801a086c5d7cc94cb7da69%2Fimage%20(736).png?alt=media" alt=""><figcaption></figcaption></figure></div>

* Click the **New dashboard +** button at the top of the panel, then click **New experience (beta)**.

<div align="left"><figure><img src="https://900295827-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7pj8v25BOyqZTdG5mdD1%2Fuploads%2Fgit-blob-fc3c89b75befe08d00901593f2ff40dcf9e5496e%2Fimage%20(614).png?alt=media" alt=""><figcaption></figcaption></figure></div>

1. Enter a **Name**.
2. Add a **Description**, if needed.

   The description appears on the homepage under the dashboard name.

   It helps people understand what the dashboard contains.
3. Click **Create**.
4. Next steps:
   * [Edit the dashboard](/basics/dashboards-new-experience/create-a-dashboard.md) - add content in the form of sections and widgets, and edit the format.
   * Publish the dashboard.
   * Share the dashboard.

#### From Flex Modes

You can also create a new dashboard directly while adding a widget, without starting from the homepage or navigation menu first.

1. In Flex Modes, set up the chart you want to add to a dashboard.
2. Click **Add to dashboard**.
3. Select **New dashboard**, then enter a name.
4. Click **Add** to create the dashboard and continue working in Flex Modes, or **Add and open** to create the dashboard and open it straight away.

This creates a new dashboard containing the widget you were working on.

5. Next steps:
   * [Edit the dashboard](/basics/dashboards-new-experience/create-a-dashboard.md) - add more sections and widgets, and edit the format.
   * Publish the dashboard.
   * Share the dashboard.


---

# 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.phocassoftware.com/basics/dashboards-new-experience/create-a-dashboard-new-experience.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.