> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/users-and-access/user-permissions/permission-presets/managing-and-updating-presets.md).

# Managing and Updating Presets

1. In the [**Admin Portal**](https://admin.gobossit.com/), go to the **group level**.
2. Navigate to **Workforce > Permission Presets**.
3. Select the **preset** you wish to modify.
4. Make the necessary **permission changes**.
5. Click **Save.**

A confirmation message will appear: *"Are you sure you want to update this permission? The changes will be applied to all staff members who have this permission assigned."*

When you save changes to a permission preset, all users that the preset is applied to will automatically receive the updated permissions. No individual staff member updates are required.

{% hint style="info" %}
**Permission changes require re-log in**.

Once permissions are updated, changes do not apply immediately during an active session. The system loads user permissions at log in. If changes are made while the user is still logged in, they must log out and log back in to see updated permissions.

Alternatively, in the POS, you can go to **Settings** then click **Clear cache and reload config**. This allows permissions to be updated without being required to log out.
{% endhint %}


---

# 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.bossithq.com/users-and-access/user-permissions/permission-presets/managing-and-updating-presets.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.