> For the complete documentation index, see [llms.txt](https://docs.interval-soft.com/interval/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interval-soft.com/interval/documentation/stakeholders/users/user-roles.md).
# User Roles
This section guides you through the process of creating and managing various roles, each with customizable levels of access to the system's features. Learn how to tailor user permissions to enhance security and operational efficiency, ensuring that every team member has the access they need.
Explore the flexibility of defining user roles within InterVal. Review the numbered labels on the screenshots below and read the associated text to learn more about the different features on this page.
## 1 - Role List Table
This screenshot provides a clear view of the User Roles main page, showcasing the ease of managing different roles within the system. Here, you can create, view, edit, and delete roles based on your organizational needs and compliance requirements.
User Roles Dashboard
1. **Create New Role Button:** The 'New Role' button is prominently displayed for easy access to start defining a new role within your system. Click this to open the role configuration page where you can set permissions and access details.
2. **Roles Overview Table:** This section of the table lists the 'admin' role, serving as an example for how roles are organized. Each role has a unique ID and name for quick identification and management.
3. **Edit Role Button:** The pencil icon represents the edit function, allowing for modification of the role’s permissions and properties. Click here to update the role to suit changing requirements or to refine access control.
4. **Delete Role Button:** The trash bin icon is used to delete a role. It's enabled only when no users are currently assigned to the role, ensuring system integrity and preventing accidental removal of active roles.
## 2 - **Role Creation and Permissions Setup**
You can access this interface by clicking on the 'New Role' button. This 'Add New Role' interface is where the precision of user access begins. Define a new role by entering name for the role and selecting the specific permissions to records and features from the comprehensive list below.
You can access a nearly identical interface for editing existing roles by clicking on the blue pencil icon 'Edit Role' button.
Role Creation and Permissions Setup
1. **Role Name Input:** Enter a unique name for the role here. The name should reflect the level of access or the job function, such as 'Administrator' or 'Valuation Analyst. You can also edit the names of existing roles.
2. **Permissions Checklist:** Check the boxes next to each page or record type to grant access. Unchecked boxes mean the role will not have any access to those items. You can also add or delete permissions for existing roles.
3. **Edit Rights Option:** When this is selected, users with the role can add, edit, or remove records on the corresponding pages, allowing full management capabilities.
4. **View-Only Rights Option:** This option limits the role to viewing records only, without the ability to make changes, suitable for roles that require oversight but not editing rights.
---
# 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.interval-soft.com/interval/documentation/stakeholders/users/user-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.