> For the complete documentation index, see [llms.txt](https://docs.rekor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rekor.ai/scout/scout-dashboard/configuration/permissions-groups.md).
# Permissions Groups
The Permissions Groups function allows an organization to set up groups that have custom permissions assigned to them. The screen displays the list of existing permissions groups and a management panel where groups are edited.
To add a new group, click New Group. Enter the Permission Group Name then click Create.
The management panel allows you to add users, add allowed cameras, and select the alert permissions for that group.
To add a new user to a group, click Add User. Click the drop down menu then select the users that will be added to the group. Click Add Users.
{% hint style="info" %}
Users added to a permission group will have all selected alert permissions applied to them.
{% endhint %}
{% hint style="info" %}
If a user is in 2 groups with conflicting permissions, the highest permission will be used.
{% endhint %}
Click the Allowed Cameras tab. You may allow all cameras, allow an RPSN search, and allow a federated search.
{% hint style="info" %}
By restricting a group to specific cameras, users in this group will only be able to search for / view results from the allowed cameras in this group.
{% endhint %}
Click the Alert Permissions tab. Assign whether the group can manage, view, or have no access to the chosen alert lists, and whether or not that group will receive email or SMS notifications from that alert list.
---
# 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.rekor.ai/scout/scout-dashboard/configuration/permissions-groups.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.
