> 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/applying-permission-preset-to-a-user.md).
# Applying Permission Preset to a User
1. In the [**Admin Portal**](https://admin.gobossit.com/), navigate to **Workforce > Users**.
2. Select relevant **user**.
3. Go to the **Permissions** tab and select the preset from the **Permission set** dropdown.
{% hint style="warning" %}
A permission set can be applied only if you already have all the permissions it includes. If you lack any permission within a set, that set appears greyed out.
{% endhint %}
A confirmation message will appear: *"Are you sure you want to change the permission set to \[permission preset]?"*
Once a preset is applied, the user's permissions will reflect those defined in the preset and individual permission toggles become read-only.
---
# 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/applying-permission-preset-to-a-user.md?ask=&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.
