> For the complete documentation index, see [llms.txt](https://docs.secureaccess.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secureaccess.com/documentation/admin-guide/permission-management.md).

# Permission management

In *SecureAccess® CLOUD* it is possible to grant or deny access to the users for every specific web application. In the subdomain section the administrator can click on the ![](/files/-Lc7CA-t7V03dy73TpvF)  button and a new screen will be shown in order to manage the permission rights for registered users and groups for that specific subdomain. 

![Image 1: Subdomain permissions management page](/files/-Lc7CG7b11pOrjnQRlIM)

By default, all users and groups are allowed to access the web application. From the screen above you can add or remove permissions for each user and groups.  

Permissions set at user level are always overriding permissions set at groups level. 


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.secureaccess.com/documentation/admin-guide/permission-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.