> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/user-administration-settings/setting-system-roles-in-agilecase.md).
# Setting System Roles in AgileCase
This lesson will cover setting up system roles in AgileCase and governing their access privileges in the system.
### Access system roles
To manage your system roles, click the "System Roles" button on the settings menu under "User Admin".
{% stepper %}
{% step %}
### Adding a new role type
System roles govern what parts of the system users have access to.
As an administrator you will have full access to the system but you may want to restrict the privileges of other uses. For example: you may not wish to give basic users access to your billing or accounts functionality.
The two default system roles are: basic users which is intended to cover any non-administrative staff that have access to AgileCase; and extranet users, which covers clients that are able to access AgileCase through client connect, which you can read about [here](/user-documentation/client-connect.md).
If you want to Add a new system role type, click the "Add Role Type" button in the top right hand corner of the page.
{% endstep %}
{% step %}
### Name your role
After choosing to add a new role type, you will be prompted to create a name for it. Fill in the text box and click "Create" to create the new system role.
{% endstep %}
{% step %}
### Edit the new role
Newly created roles are granted no system access as a default. to edit a role's privileges, click on the dropdown arrow then "Edit" to open the editing page. Existing roles can also be edited in the same way.
{% endstep %}
{% step %}
### Selecting role privileges
On the edit role type screen you can enable or disable access to certain parts of the system for users of that type. To do this simple choose whether you want an option to be enabled or disabled in corresponding dropdown menu.
{% endstep %}
{% step %}
### Changing a users system role
To apply your new system role to a user, go to the user page using the button under "User Admin" and select the user you want to edit. On their page, use the "System Role" dropdown at the bottom of the page and select the new system role.
Once you have saved these changes, the user will have access to their new privileges upon their next log in to the system.
{% endstep %}
{% step %}
### New privileges
When the user next logs in, the areas of the system that have been enabled or disabled for their roles will be either visible or invisible depending on their permissions.
{% endstep %}
{% step %}
### Disabling a role
If you want to completely disable a role and send it to the recovery bin, open the dropdown menu and click "Disable". To learn how to recover a disabled role from the recovery bin, click [here](/administrator-documentation/system-settings/recovering-deleted-items.md).
{% endstep %}
{% endstepper %}
---
# 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.agilecase.com/administrator-documentation/user-administration-settings/setting-system-roles-in-agilecase.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.