> 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/about-back-office.md). # About Back Office ### Overview The **Back Office** section provides access to configuration and administrative functions used to manage and maintain DinePlan. It brings together features that help users configure system settings, manage printers and products, configure tickets, manage accounts and automation, maintain entities and users, and handle feedback. The available options in the Back Office section are: #### Accessing the Back Office To access the **Back Office** section: 1. Log in to DinePlan. 2. From the **Dashboard**, select **“Back Office”**.
3. The Back Office screen opens with the available options. 4. Select the required option to access its respective functionality. #### Back Office Functions The Back Office features support different aspects of system configuration and administration. Each option provides tools for managing a specific area of DinePlan and helps maintain the required settings for restaurant operations. * [**Settings**](/dineplan/backoffice/settings.md) – Manage general system and operational configurations. These settings help configure DinePlan according to the restaurant's operational requirements. * [**Printer**](/dineplan/backoffice/printer.md) – Configure printer-related settings for POS operations. This includes managing the printer configurations required for printing bills, tickets, and other POS information. * [**Products**](/dineplan/backoffice/products.md) – Manage and configure products used in the POS. Users can maintain product-related information and settings required for ordering and billing. * [**Tickets**](/dineplan/backoffice/tickets.md) – Manage ticket-related configurations and settings. These options help control how tickets are configured and handled during restaurant operations. * [**Accounts**](/dineplan/backoffice/accounts.md) – Manage account-related configurations. This section provides options for maintaining account information and related settings within DinePlan. * [**Automation**](/dineplan/backoffice/automation.md) – Configure available automated processes and functions. These options help simplify recurring or system-driven activities. * [**Entities**](/dineplan/backoffice/enitites.md) – Manage and configure entities used within the system. This helps maintain the different entities and their associated configurations. * [**Users**](/dineplan/backoffice/users.md) – Manage users and their access to DinePlan. This allows authorized users to maintain user information and control access based on the required permissions. * [**Feedback**](/dineplan/backoffice/feedback.md) – Access and manage feedback-related activities. This provides a dedicated area for handling feedback associated with the application or its operations. --- # 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/about-back-office.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.