> 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/settings/license-information.md).

# License Information

### **Overview** <a href="#overview.14" id="overview.14"></a>

The **License Information** section displays the license details associated with the DinePlan application.

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

### **Screen Elements** <a href="#screen-elements.13" id="screen-elements.13"></a>

| **Screen Element** | **Description**                                                    |
| ------------------ | ------------------------------------------------------------------ |
| License Name       | Displays the name associated with the license.                     |
| Terminal Count     | Displays the number of terminals included in the license.          |
| Expiry Date        | Displays the license expiry date.                                  |
| DineFly Count      | Displays the DineFly count associated with the license.            |
| Version            | Displays the current DinePlan application version.                 |
| Last Update Date   | Displays the date when the application was last updated.           |
| Is Single Terminal | Indicates whether the license is configured for a single terminal. |
| License            | Displays the available license information.                        |
| CountryCode        | Displays the country code associated with the license.             |
| "Close"            | Closes the License Information screen.                             |

### **Working** <a href="#working.12" id="working.12"></a>

1. Open "License Information".
2. Review the displayed license details.
3. Check the License Name, Terminal Count, Expiry Date, and other available license information.
4. Review the Version and Last Update Date when required.

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

5. Click "Close" to exit the screen.

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

### **Use Case** <a href="#use-case.12" id="use-case.12"></a>

1. View the license details configured for the DinePlan application.
2. Verify the license name associated with the installation.
3. Check the number of licensed terminals.
4. Review the license expiry date.
5. Verify the DineFly count associated with the license.
6. Check the current application version.
7. Review the last update date.
8. Verify the country code and single-terminal configuration.

### **Notes** <a href="#notes.12" id="notes.12"></a>

* The License Information screen is primarily used to view license-related details.
* The displayed values depend on the license configuration of the application.
* No configuration changes are performed from this screen.


---

# 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/settings/license-information.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.
