> 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/customize-action-bar.md).

# Customize Action Bar

## Overview

The Action Bar is the set of quick-action buttons displayed in the patient profile in the Care Portal. It allows care team members to perform common actions – like creating an encounter, sending a message, or adding a task – directly from the patient view without navigating away. You can customize which actions appear in the Action Bar for each role.

***

## Default Action Bar Items

By default, the Action Bar may include:

* **New Encounter** – start a new encounter with the patient
* **Send Message** – open the communication composer
* **Add Task** – create a task for this patient
* **Enroll in Program** – add the patient to a care program

***

## Customizing the Action Bar

1. In the Designer, navigate to **Action Bar** or **Customize Action Bar**.
2. Select the role or profile you want to customize.
3. Add or remove actions from the available list.
4. Set the display order.
5. Save and publish.

***

## Role-Based Customization

The Action Bar can be configured differently per role. For example:

* Care Managers see "Send Message" and "New Encounter"
* Supervisors see "View Audit" and "Change Region"
* Read-only users have no action bar items

***

## Publishing

Create a draft in the Designer and publish to apply Action Bar changes 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/customize-action-bar.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.