> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/system-admins/administration/company/users/manage-user-permission.md).

# Manage Security Groups and App Permissions

Manage Security Groups and review application access in Company.

Security Groups bundle permissions for a role. App Permissions provides an application-centered view of those permissions and the users who receive access.

## Review a Security Group

1. Open the **Company App**.
2. Go to `Users` > `Security Groups`.
3. Search for the group.
4. Select the group.
5. Review:
   * User access
   * Permissions
   * Authorizations

Use the group details page when you need to understand or change one role.

## Create a Security Group

1. Go to `Security Groups`.
2. Click the create button.
3. Enter the group name, ID, and description.
4. Save the group.
5. Open the new group.
6. Add the permissions approved for the role.
7. Add users only after the permission list is reviewed.

Use a stable ID. The group name and description can explain the business role.

## Change a Security Group

1. Open the group.
2. Review current users and permissions.
3. Edit the group name or description when needed.
4. Add or remove the intended permissions.
5. Save the changes.
6. Test with a user assigned to the group.

Removing a permission affects every user who receives it through that group. Check whether another Security Group still grants the same permission before concluding that access was removed.

## Review App Permissions

Use App Permissions when you start with an application or capability instead of a role.

1. Go to `Users` > `App Permissions`.
2. Select an application.
3. Select a permission.
4. Review:
   * Security Groups with access
   * Assignment history
   * Users with access
5. Open the relevant Security Group to make an approved change.

The catalog reflects the permissions available in the current OMS environment. Use it instead of a copied static permission list.

## Verify a change

1. Confirm that the user belongs to the expected Security Group.
2. Confirm that the group contains the required permission.
3. Ask the user to sign out and sign in again when access remains unchanged.
4. Open the exact page or action being tested.

See [Troubleshoot application access](/documents/system-admins/administration/company/users/troubleshooting/application-access-issue.md) when the task remains unavailable.


---

# 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.hotwax.co/documents/system-admins/administration/company/users/manage-user-permission.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.