> 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/faqs.md).

# FAQ's

## 1. How do I create a new user profile for a restaurant staff member?

To set up a new user profile in DinePlan BackOffice:

1. Open **BackOffice** and navigate to the **Users** setting screen.
2. Select **"Add User"**.
3. Enter the employee's name in the **"User Name"** field.
4. Enter the security login PIN in the **"Pin"** field.
5. Enter a security code in the **"Security Code"** field.
6. Click **"User Role"** and select the required role for the user from the dropdown menu.
7. Click **"UI Language"** and select the primary interface language.
8. Select an **"Alternate Language"** if a secondary interface language is required.
9. Select **"Save"** to create the user account.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-f54ba6414595d7e78ad4521aa84a7b42aa8ffdfb%2FScreenshot%202026-10-14%20083158.png?alt=media" alt=""><figcaption></figcaption></figure>

**Note:** **User Name**, **Pin**, **User Role**, and **UI Language** are required when creating a user.

## 2. Which fields are strictly mandatory when creating a new user profile?

When creating a new user profile in DinePlan BackOffice, you must complete four mandatory fields before the system allows you to save the record:

* **User Name:** Specifies the name of the user.
* **Pin:** Specifies the PIN used by the user for authentication.
* **User Role:** Specifies the role assigned to govern user access.
* **UI Language:** Specifies the primary language used in the DinePlan interface.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-4973292f9ac586ad70d61b56f8ee57209e55c698%2Fimage%20(356).png?alt=media" alt=""><figcaption></figcaption></figure>

## 3. What are the PIN length requirements when setting up a user PIN?

When entering a user PIN in the **Pin** field, the PIN must contain **between 4 and 20 characters**.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-e0a1ed84938dc28504d08ed06e646fc35ccd8457%2Fimage%20(355).png?alt=media" alt=""><figcaption></figcaption></figure>

## 4. How do I assign a specific User Role to a staff member?

To assign operational access privileges to a user:

1. Open the user creation or edit screen (**Add User** or **Edit User**).
2. Locate the **"User Role"** field.
3. Click the **"User Role"** dropdown menu and select the required role for the user.
4. Select **"Save"** to store the user details.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-52e84584b10403130f8961e189443ae7072c3496%2Fimage%20(354).png?alt=media" alt=""><figcaption></figcaption></figure>

## 5. How do I set the primary UI Language and Alternate Language for a user?

To configure language preferences for a user profile:

1. Open **Add User** or **Edit User** on the **Users** settings screen.
2. Click the **"UI Language"** dropdown menu and select the primary language used in the DinePlan interface.
3. Click the **"Alternate Language"** dropdown menu and select a secondary language if required.
4. Select **"Save"**.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-be388f8fb0f5405ad3efa9ffdc6f80ad1fde19d9%2Fimage%20(353).png?alt=media" alt=""><figcaption></figcaption></figure>

## 6. Where do I enter a security code for a user account?

In the user setup window (**Add User** or **Edit User**), locate the **"Security Code"** field. Enter the required security code assigned to the user, then select **"Save"** to store the entry.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-2e6440a7eb85470ccc98def155db858c4a39930a%2Fimage%20(352).png?alt=media" alt=""><figcaption></figcaption></figure>

## 7. How do I update an existing user's login details or assigned role?

To edit an existing user account:

1. Open the **Users** setting screen in BackOffice.
2. From the **User List**, select the user profile you want to modify.
3. Select **"Edit User"**.
4. Update the required user details (such as **User Name**, **Pin**, **Security Code**, **User Role**, **UI Language**, or **Alternate Language**).
5. Select **"Save"** to save your changes.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-ff4ae75f2b937f78a07c20fa52502104f42cee74%2Fimage%20(351).png?alt=media" alt=""><figcaption></figcaption></figure>

## 8. How do I delete a user account from DinePlan when an employee leaves?

To permanently remove a user profile from the system:

1. Open the **Users** screen in BackOffice.
2. Highlight or select the target user from the **User List**.
3. Select **"Delete User"**.
4. A confirmation message will be displayed on screen.
5. Select **"Yes"** to delete the user.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-7897227b8ca5234534021f4591c9678dabed05c4%2Fimage%20(350).png?alt=media" alt=""><figcaption></figcaption></figure>

**Note:** A confirmation is strictly required before deleting a user.

## 9. What happens if I click "No" on the user deletion confirmation window?

If you select **"No"** when the deletion confirmation message appears, the deletion operation is cancelled and the user account remains unchanged in the **User List**.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-f9cb9c56722e24e575f15b13a6856a43b1cf7f5b%2Fimage%20(349).png?alt=media" alt=""><figcaption></figcaption></figure>

## 10. How do I change the display order of users in the User List?

To customize the order in which users are displayed on screen:

1. Open the **Users** setting screen.
2. Select **"Change Sort Order"**.
3. Arrange the users in the required display order.
4. Save the updated order.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-e6a45f49a5e5043ac1e3e125f5f3ec33dbaa076a%2Fimage%20(348).png?alt=media" alt=""><figcaption></figcaption></figure>

## 11. How do I search for a specific user profile in BackOffice?

To quickly locate a user in BackOffice:

1. Open the **Users** settings screen.
2. Click inside the **"Search"** input box located above the **User List**.
3. Type the user's name or keyword.
4. The **User List** automatically filters to display matching user records.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-d95eba210612c215929af36c811ec1b78214d2d5%2Fimage%20(347).png?alt=media" alt=""><figcaption></figcaption></figure>

## 12. How do I create a new User Role in BackOffice?

To create a new role for categorizing users and governing permissions:

1. Open **BackOffice** and navigate to **User Roles**.
2. Select **"Add User Role"**.
3. Enter the role name in the **"Role Name"** field.
4. Click **"Department"** and select the department associated with the role.
5. Configure the **"Admin"** option if administrator access is required.
6. Expand the required permission sections and configure permissions.
7. Select **"Save"** to create the user role.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-0e8d6741aa03257c8b260b3f06d2bf637ff709cc%2Fimage%20(346).png?alt=media" alt=""><figcaption></figcaption></figure>

**Note:** **Role Name** and **Department** are required when creating a user role.

## 13. Which fields are compulsory when creating a new User Role?

When creating a new user role in BackOffice, you must specify:

* **Role Name:** Specifies the descriptive label for the user role.
* **Department:** Specifies the department associated with the user role.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-5b9b1bae9bc557581ac819d9551769a5ed5c5421%2Fimage%20(345).png?alt=media" alt=""><figcaption></figcaption></figure>

## 14. How do I configure administrator access for a User Role?

To enable or disable administrator access for a specific user role:

1. Open **Add User Role** or **Edit User Role** on the **User Roles** screen.
2. Locate the **"Admin"** option.
3. Configure the **"Admin"** option to enable or disable administrator access for the role.
4. Select **"Save"**.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-7cbb7427f0afac8885e2590be1432e2a6e0c08aa%2Fimage%20(343).png?alt=media" alt=""><figcaption></figcaption></figure>

## 15. How do I assign a Department to a User Role?

To associate a user role with a specific operational department:

1. Open the user role setup screen (**Add User Role** or **Edit User Role**).
2. Locate the **"Department"** field.
3. Click the dropdown list and select the required department.
4. Select **"Save"**.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-6b8ad56b176c50aa47e3677d3e531c6653da2b7e%2Fimage%20(342).png?alt=media" alt=""><figcaption></figcaption></figure>

## 16. How do I configure Reporting Permissions and Ticket Permissions for a User Role?

To grant or restrict reporting and ticket access for a role:

1. Open **Add User Role** or **Edit User Role**.
2. Locate **"Reporting Permissions"** and click to expand the section to configure reporting settings.
3. Locate **"Ticket Permissions"** and click to expand the section to configure ticket-related settings.
4. Select **"Save"** to store permission changes.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-a98e76d13b029eecbe1cd1ec64a0942ecd94437d%2Fimage%20(341).png?alt=media" alt=""><figcaption></figcaption></figure>

## 17. How do I set up WorkDay, Navigation, Department, and Kitchen Permissions for a role?

To manage WorkDay, system navigation, department, and kitchen operations access:

1. Open the user role configuration screen (**Add User Role** or **Edit User Role**).
2. Expand **"WorkDay Permissions"** to configure WorkDay settings.
3. Expand **"Navigation Permissions"** to configure navigation settings.
4. Expand **"Department Permissions"** to configure department settings.
5. Expand **"Kitchen Permission"** to configure kitchen operation permissions.
6. Select **"Save"**.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-bbd1f3e7af3b731e0eaaa83ddc3c03595292e57d%2Fimage%20(340).png?alt=media" alt=""><figcaption></figcaption></figure>

## 18. How do I edit an existing User Role's permissions or details?

To modify permissions or settings for an existing role:

1. Open **User Roles** in BackOffice.
2. Select the required user role from the **User Role List**.
3. Select **"Edit User Role"**.
4. Update the required role details (**Role Name**, **Department**, **Admin**) or expand permission sections to update access settings.
5. Select **"Save"** to save your changes.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-7bb8c7ea341274d36bc71748663e204b39795f44%2Fimage%20(339).png?alt=media" alt=""><figcaption></figcaption></figure>

## 19. How do I delete an unneeded User Role, and what confirmation is required?

To remove a user role from the system:

1. Go to the **User Roles** screen in BackOffice.
2. Select the user role you want to delete from the **User Role List**.
3. Select **"Delete User Role"**.
4. A confirmation message is displayed on screen.
5. Select **"Yes"** to confirm deletion, or select **"No"** to cancel.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-7abe8b78f97b3b101993dbfa2df5374e0cb473af%2Fimage%20(338).png?alt=media" alt=""><figcaption></figcaption></figure>

**Note:** A confirmation is strictly required before deleting a user role.

## 20. How do I reorder User Roles in the User Role List?

To control how user roles are presented in selection lists:

1. Open the **User Roles** screen in BackOffice.
2. Select **"Change Sort Order"**.
3. Arrange the user roles in the required order.
4. Save the updated display order.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-61b9e82b67f4927e336a4c1374545d9ad7bba04e%2Fimage%20(337).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/faqs.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.
