> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/visualize-and-organize-your-data/create-and-customize-pages.md).

# Create and customize pages

Pages give you a flexible space to shape how people work with your app, for example by building dashboards that bring important information together in a clear, useful way. Add charts, metric cards, buttons, and filtered views to help users focus on what matters most and make daily work feel faster and easier.

When you add forms or views, keep the layout focused:

* Use tabs, headings, spacing, and line breaks to group related content.
* Hide technical fields with conditional display rules or user-specific access.
* Create filtered views so users can find records faster.

## **Create a page**

{% stepper %}
{% step %}
**Open the page menu**

In the app navigation, click the arrow next to **+ Create table**.\
Select **Create page**.
{% endstep %}

{% step %}
**Enter the page name**

Enter a value in **Name**.\
Ninox creates the **Internal name** automatically.\
Change the **Internal name** only if you need a different value.
{% endstep %}

{% step %}
**Choose an icon and color**

Click the icon picker.\
Select an icon and a color for the page.\
Click **Confirm** to apply your choice.
{% endstep %}

{% step %}
**Create the page**

Click **Create page**.\
The new page appears in the app navigation.
{% endstep %}
{% endstepper %}

## **Build a dashboard on the page**

Use the page as a dashboard to highlight the data that matters most.

{% stepper %}
{% step %}
**Add dashboard widgets**

Open the page in **Builder mode**.\
In the right panel, open **Add**.\
Add the views and components you need.
{% endstep %}

{% step %}
**Choose how to visualize the data**

Use widgets such as:

* **Charts** for trends and comparisons
* **Kanban** for stage-based work
* **Metric cards** for key numbers
* **Map** for location-based data
  {% endstep %}

{% step %}
**Configure each widget**

Select a widget on the page.\
Open **Settings** in the right panel.\
Adjust the data source, display, and behavior for that widget.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Start with one or two widgets first. Then refine the layout after the data displays correctly.
{% endhint %}

## **Share a dashboard without showing source tables**

Pages work well when users need insight from several tables, but do not need to work in those tables directly.

For example, you can create one dashboard that combines data from several related tables, such as projects, tasks, and invoices. That dashboard can stay visible for workspace users who can access the app, including users with the **Viewer** role.

To keep the interface focused, hide the source tables from the app navigation and leave the dashboard visible. This gives users one clear place to review key information.

Keep in mind that hiding a table from navigation only removes it from the menu. If the source tables contain sensitive data, also use table and field permissions to control who can read the underlying records and fields. For more on roles and permissions, see [Manage workspace access](/builder-hub/manage-your-organization-and-workspace/organize-your-workspace/manage-workspace-access.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 dynamically by asking a question.

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

```
GET https://docs.ninox.com/builder-hub/visualize-and-organize-your-data/create-and-customize-pages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.