> For the complete documentation index, see [llms.txt](https://aeudoc.gitbook.io/developer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aeudoc.gitbook.io/developer/application-features/access-control.md).

# Access Control

## Registering Actions

When an Action has been added to a Controller, it needs to be registered first to be able to use it.

To register Actions, do the following steps:

1. In the navigation bar of the application, click "Settings" >"Access Assignment"
2. Click "Synch" Button in the Toolbar
3. Select the respective Controller in the "Resource Group" Dropdown List
4. Check all the Actions you want to add
5. Click the "Save" Button in the Toolbar

<figure><img src="/files/K89gKpJlrIp5JnnrEw7W" alt=""><figcaption></figcaption></figure>

## Linking Actions to Roles

When Actions are being registered, they are linked to the Role "ADMINISTRATOR", which is the default value of the User Role drop down:

<figure><img src="/files/ZO5DsUgnBLvQ4QewiYT8" alt=""><figcaption></figcaption></figure>

"ADMINISTRATOR" is the Role that has access to all Actions. However, not all Users are allowed to use all Actions, which is why a User can be assigned different Roles (see [Account Management](/developer/application-features/account-management.md)).

To link Actions to Roles, i.e. to specify which Actions a specific Role is allowed to execute, do the following steps:

1. Select the Role in the User Role drop down
2. Check all the Actions the selected Role is allowed to use and make sure that Actions they may not executed are unchecked
3. Click the "Save" Button in the Toolbar&#x20;

## Maintaining Roles

The "Access Controls" page is also the place where Roles can be created, edited and deleted. In the following, each of these processes will be described step-by-step:

### Creating a New Role

1. Click the "Roles" Button and select "Add New Role.." from the drop down options
2. Enter the Name of the new Role and optionally write a Description
3. Click the "Save" Button in the Modal

<figure><img src="/files/FN9hXPz1mHGY7hkO4cj3" alt=""><figcaption></figcaption></figure>

### Editing an Existing Role

1. Click the "Roles" Button and select "Add New Role.." from the drop down options
2. Edit the Description (Name cannot be edited)
3. Click the "Update" Button in the Modal

<figure><img src="/files/WjrzK3EnS2s36sIkNd1u" alt=""><figcaption></figcaption></figure>

### Deleting an Existing Role

1. Make sure that the Role you want to delete is selected in the User Role drop down
2. Click the "Roles" Button and select "Delete Role.." from the drop down options


---

# 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://aeudoc.gitbook.io/developer/application-features/access-control.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.
