> 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/enitites/entity.md).
# Entity
### **Overview**
The Entity feature allows administrators to create and manage entities such as tables and members within DinePlan. It provides options to add individual entities, edit existing entities, delete entities, create multiple entities at once using Batch Create Entities, and change the order in which entities are displayed.
This helps administrators maintain entity records efficiently and organize them according to operational requirements.
### **Screen Elements**
| **Screen Element** | **Description** |
| --------------------- | -------------------------------------------------------- |
| Entity List | Displays the available entities grouped by entity type. |
| Search | Allows users to search for a specific entity. |
| Add Entity | Opens the screen to create a new entity. |
| Edit Entity | Opens the selected entity for editing. |
| Delete Entity | Deletes the selected entity after confirmation. |
| Batch Create Entities | Allows multiple entities to be created at the same time. |
| Change Sort Order | Allows users to rearrange the order of entities. |
| Entity Type | Specifies the type of entity being created. |
| Warehouse | Specifies the warehouse associated with the entity. |
| Account | Specifies the account associated with the entity. |
| OK | Confirms the batch creation or sort order changes. |
| Cancel | Cancels the current operation. |
| Close | Closes the Entity screen. |
### **Working**
#### **Add an Entity**
1. From the Entity List, select "Add Entity".
2. Select the required entity type in "Entity Type".
3. Enter or select the required "Warehouse".
4. Enter or select the required "Account".
5. Select "Save" to save the entity.
#### **Edit an Entity**
1. From the Entity List, select the required entity.
2. Select "Edit Entity".
3. Update the required entity details.
4. Select "Save" to save the changes.
#### **Delete an Entity**
1. From the Entity List, select the entity you want to remove.
2. Select "Delete Entity".
3. A confirmation message is displayed.
4. Select "Yes" to delete the entity or "No" to cancel the operation.
#### **Batch Create Entities**
1. From the Entity List, select "Batch Create Entities".
2. Enter the entity names, with each entity on a separate line.
3. Select "OK" to create the entities.
#### **Change Sort Order**
1. From the Entity List, select "Change Sort Order".
2. Adjust the order of the entities as required.
### **Use Case**
* Create individual entities for managing operational records such as tables or members.
* Create multiple entities at once using the "Batch Create Entities" option.
* Edit existing entity details when configuration or operational requirements change.
* Delete entities that are no longer required.
* Search for specific entities when managing a large list of records.
* Associate an entity with the required warehouse and account during configuration.
* Arrange entities in a preferred order for easier identification and navigation.
* Maintain organized entity records according to the operational requirements of the restaurant.
### **Notes**
* The "Entity Type" must be selected when creating an entity.
* The "Batch Create Entities" option creates an entity for each line entered.
* Deleting an entity requires confirmation before removal.
* Use "Change Sort Order" to rearrange the display order of entities.
---
# 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/enitites/entity.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)
