> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/backoffice/users/user-roles.md).
# User Roles
### **Overview**
The User Roles setting allows administrators to create and manage roles for users in DinePlan. Each role can be associated with a department and configured with specific permissions. Existing roles can also be edited, deleted, or arranged in the required order.
### **Screen Elements**
| **Screen Element** | **Description** |
| ---------------------- | ----------------------------------------------------------- |
| User Role List | Displays the list of existing user roles. |
| Search | Allows users to search for a specific user role. |
| Add User Role | Creates a new user role. |
| Edit User Role | Opens the selected user role for editing. |
| Delete User Role | Deletes the selected user role after confirmation. |
| Change Sort Order | Allows users to change the display order of user roles. |
| Role Name | Specifies the name of the user role. |
| Department | Specifies the department associated with the user role. |
| Admin | Enables or disables administrator access for the role. |
| Reporting Permissions | Provides permission settings related to reporting. |
| Ticket Permissions | Provides permission settings related to tickets. |
| WorkDay Permissions | Provides permission settings related to WorkDay. |
| Navigation Permissions | Provides permission settings related to navigation. |
| Department Permissions | Provides permission settings related to departments. |
| Kitchen Permission | Provides permission settings related to kitchen operations. |
| Save | Saves the new role or changes made to an existing role. |
| Close | Closes the User Role screen. |
### **Working**
#### **Add User Role**
1. Select "Add User Role".
2. Enter the "Role Name".
3. Select the required "Department".
4. Configure the "Admin" option, if required.
5. Expand the required permission sections and configure the permissions.
6. Select "Save" to create the user role.
#### **Edit User Role**
1. Select the required user role from the list.
2. Select "Edit User Role".
3. Update the required role details or permissions.
4. Select "Save" to save the changes.
#### **Delete User Role**
1. Select the user role you want to delete.
2. Select "Delete User Role".
3. A confirmation message is displayed.
4. Select "Yes" to delete the role or "No" to cancel.
#### **Change Sort Order**
1. Select "Change Sort Order".
2. Arrange the user roles in the required order.
3. Save the updated order.
### **Use Case**
* Create roles for different categories of users.
* Assign a department to a user role.
* Configure administrator access for a role.
* Control access to reporting features.
* Configure ticket-related permissions.
* Manage WorkDay-related permissions.
* Control navigation and department permissions.
* Configure kitchen-related permissions based on the role.
### **Notes**
* Role Name and Department are required when creating a user role.
* Permission categories can be expanded to configure the required access.
* A confirmation is required before deleting a user role.
* Use "Change Sort Order" to control how user roles are displayed in the list.
---
# 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://help.rbsgo.com/dineplan/backoffice/users/user-roles.md?ask=&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.
.png?alt=media)
