> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/users-and-access/user-profile-types.md).

# User Profile Types

## Role Hierarchy

1. Owner
2. Senior Manager
3. Manager
4. Supervisor
5. Staff
6. Driver

## Profile Type-Based Access and Visibility

#### Staff Visibility

Users can **only view and manage users below them**. For example:&#x20;

* An Owner can view and manage **all other roles**.
* A Manager can view and manage Supervisors, Staff, and Drivers, but not Owners, Senior Managers, and other Managers.

> **Note**: A user cannot view or edit their own permissions. Only someone in a higher role can make such changes.

## Profile Type Specifics

#### Admin Portal Access

Staff and Drivers **cannot** use the Admin Portal.

#### Personal PIN Log In

Staff cannot log in to the POS using their phone number and Personal PIN. Only the Venue PIN works for Staff.

#### Order Visibility in the POS

The system automatically limits what orders different users can see based on their profile type. Lower-level users (like drivers and staff) can only see orders for the current shift, while managers and supervisors can see orders for the current shift plus future orders. Owners and senior managers can see everything, including past orders.&#x20;

#### Payment Method Visibility

Drivers can **never** view payment methods.


---

# 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://docs.bossithq.com/users-and-access/user-profile-types.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.
