> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/basics/markdown.md).

# Restaurant Portal

The single portal through which users can access and  manage different applications of the UrbanPiper ecosystem. When working with the Business Manager, you will commonly encounter references to **Atlas** and **Prime.**&#x20;

### **Atlas – Business Manager**

This is the section which contains all the tools required for you to manage your back-of-house operations.

### Prime – Store Manager

This is the section which contains all the tools required for you to manage your front-of-house operations.

{% hint style="info" %}
While there is no explicit distinction between **Atlas** and **Prime** when you are navigating within the Business Manager, it helps to keep this distinction in mind when thinking about granting access to users based on their role in a front-of-house or back-of-house capacity.
{% endhint %}

To learn more about using the Business Manager, check out our [articles](/business-manager/introduction.md) about it.


---

# 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.urbanpiper.com/basics/markdown.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.
