> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/app-maker/team-and-access/users-and-roles.md).

# Users & Roles

## <mark style="color:red;">Users​</mark> <a href="#users" id="users"></a>

User settings on AppMaker are managed through the Users page. A user is specifically defined as an individual who logs into the platform.

Within this page, all users affiliated with the organization, along with their authorizations and authorization groups, can be easily viewed. By selecting the Users menu item, administrators can effortlessly add new users or edit existing ones.

The system's current users are listed in a user-friendly manner, with a summary table showcasing their general information for quick reference.

### Add User​ <a href="#add-user" id="add-user"></a>

**Step 1: Access the Users Screen​**

* Open App Maker and navigate to the **Settings > Users** tab.
* A list of existing users will be seen on the Users screen.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F4UDQqMbauIOZLJUSm9vy%2Fimage.png?alt=media&amp;token=b11d951c-466c-443a-8270-b7b682e5e1ba" alt=""><figcaption></figcaption></figure>

**Step 2: Add a New User​**

* To add a new user to the organization, click the **Add User** button on the list screen.
* When you enter the user's email, the list shows every user who is not already a member of this organization — including people who already belong to another organization, who can now be members of both. People who already belong to 10 organizations, the most one account can join, are not listed.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FwGCOZjcMolkXO3Cn4KXI%2Fimage.png?alt=media&amp;token=cdbff169-7573-4ba7-8f6f-2a24ef8b99e8" alt=""><figcaption></figcaption></figure>

**Step 3: Fill in User Details​**

* On the user creation page, provide all the necessary information, such as user and roles for the new user.
* Roles are assigned to users based on the authorization preferences.
* Notably, a single user can have multiple roles, granting them various permissions within the platform.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FEBTOH87Ul9STSRfLuraX%2Fimage.png?alt=media&amp;token=73174666-532b-4612-a411-5c6f4713d90c" alt=""><figcaption></figcaption></figure>

**Step 4: Role Privileges​**

* To get a comprehensive understanding of each role and its associated authorizations, consult the **Privileges** table.
* The table displays a breakdown of the actions authorized for pre-defined user and role types.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F1PKIfO06Jmu6hO0ouoJ3%2Fimage.png?alt=media&amp;token=eef5bccd-1060-421e-9a68-14ec3fba7bb2" alt=""><figcaption></figcaption></figure>

### Edit User​ <a href="#edit-user" id="edit-user"></a>

**Step 1: Find the User to Edit​**

* Look through the list of users to locate the specific user whose settings are desired to change.

**Step 2: Edit User​**

* At the end of the user's row, click on the **Edit** icon.
* The **Edit** (and delete) actions are only available to the organization owner. If you don't manage the organization, the actions column is hidden and these icons won't appear.

**Step 3: Modify Information​**

* A new screen will appear with the user's details.
* Update any necessary information.
* Adjust the user's roles as required.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2Fl2yq37OTsdMKyvHAazP3%2Fimage.png?alt=media&amp;token=b5dcd847-c904-4c09-949a-fd3252e9c8ee" alt=""><figcaption></figcaption></figure>

**Step 4: Send Changes​**

* After making the desired changes, save the updates to apply the edited settings.

## <mark style="color:red;">Roles​</mark> <a href="#roles" id="roles"></a>

Roles are a specific set of authorization rules assigned to users. Within App Maker, there are predefined roles that users can utilize, and they also have the flexibility to create custom roles tailored to their preferences.

The Roles page provides an overview of all the roles added under users' organization, allowing them to manage and assign authorizations efficiently.

### Create Role​ <a href="#create-role" id="create-role"></a>

**Step 1: Access the Roles Screen​**

* Open AppMaker and navigate to the **Settings > Roles** section.
* A list of existing roles will be seen on the Roles screen.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FcsRluumGuiO1VRfzP4mN%2Fimage.png?alt=media&amp;token=6e0a96cc-51da-40f1-8261-f6fb731fd6db" alt=""><figcaption></figcaption></figure>

**Step 2: Create a New Role​**

* Click on the **ADD NEW ROLE** button to create a new role.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FLtkhw3vuYsGKhE6O8Xtj%2Fimage.png?alt=media&amp;token=2323ebd0-e27a-4f38-b4bc-fb1d15906f4d" alt=""><figcaption></figcaption></figure>

**Step 3: Fill in Role Details​**

* On the new role creation page, provide the required role information.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FbdNH6Tdmo5TNDzkb5S6Q%2Fimage.png?alt=media&amp;token=d8491120-159b-4934-90bf-23e152736d69" alt=""><figcaption></figcaption></figure>

**Step 4: Assign Privileges​**

* Next, assign specific authorizations to the new role.
* In the **Privileges** list, choose the permissions want to grant to the role.

### Edit Role​ <a href="#edit-role" id="edit-role"></a>

**Step 1: Find the Role to Edit​**

* Look through the list of roles to locate the specific role whose settings are desired to change.

**Step 2: Edit Role​**

* At the end of the role's row, click on the **Edit** icon.

**Step 3: Modify Information​**

* A new screen will appear with the role's details.
* Update any necessary information, such as role name and privilege settings.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2F7QiKHifvvZxAHnQXCXyP%2Fimage.png?alt=media&amp;token=46272961-0910-4482-8a44-819fc35d1416" alt=""><figcaption></figcaption></figure>

**Step 4: Send Changes​**

* After making the desired changes, remember to save the updates to apply the edited settings.


---

# 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.akinon.com/tutorials/app-maker/team-and-access/users-and-roles.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.
