> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/core/people/setting-permissions-for-users/setting-up-roles.md). # Setting Up Roles ## 1 - Creating Roles 1. Click the "+ button" at the top right of the screen, select "Create".

2. Create your role name and select permissions for the role.

3. You are able to select permissions across any of our products you have access to for your roles. 4. Once you have selected all the permissions for the role you are creating, click "Save".

## 2 - Assigning Roles When adding a new user you are able to assign a predetermined role to the user. 1. Under "Core > People" click on the "+ button" and select "Create".

2. Input your User's information into the first page, then select "Next". 3. Select the role the user is assigned to. You can click the "eye" icon to see what the user will have permissions for in this role. If this user needs to have additional permissions, toggle the custom permissions and select any other permissions they need. Click "Next" to move on to "Custom Values".

4. Add any custom values you may need, and then finish the user's permissions by saving on the final screen.

--- # 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.adminremix.com/core/people/setting-permissions-for-users/setting-up-roles.md?ask=&goal= ``` `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.