> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/designer/navigation-and-layout/how-to-create-navigation-layouts.md).

# How to Create Navigation Layouts

## Overview

Navigation layouts in the Designer control the structure of the left-hand sidebar menu in the Care Portal. Each role can have a different navigation layout – allowing you to show only the pages and features relevant to each user type.

***

## How Navigation Layouts Work

* A navigation layout is a menu configuration tied to one or more roles.
* It defines which items appear in the Care Portal sidebar and in what order.
* Items that are not included in the layout are not visible to users with that role.

***

## Creating a Navigation Layout

1. In the Designer, navigate to **Navigation** or **Navigation Layouts**.
2. Click **+ Add Layout** or create a new draft.
3. Enter a **Name** for the layout.
4. Select the **roles** this layout applies to.
5. Add **menu items** from the available list:
   * Homepage
   * Patients / My Patients
   * Calendar
   * Inbox
   * Tasks
   * Reports / Insights
   * Custom pages or links
6. Set the **order** of items by dragging them into position.
7. Save and publish.

***

## Adding the Inbox to Navigation

The Inbox must be explicitly added to the navigation layout for each role that requires access. See [Inbox](https://docs.welkinhealth.com/care/communication/inbox#the-designer-portal) for permission requirements.

***

## Role-Specific Layouts

Different roles typically have different navigation needs:

* **Care Managers** – Patients, Calendar, Inbox, Tasks
* **Supervisors** – Patients (all), Insights, Reports
* **Administrators** – limited Care Portal access, primarily administrative views

***

## Publishing

Create a draft in the Designer and publish to apply the navigation layout to the Care Portal.


---

# 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.welkinhealth.com/designer/navigation-and-layout/how-to-create-navigation-layouts.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.