> For the complete documentation index, see [llms.txt](https://docs.kbgfuzion.com/erp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kbgfuzion.com/erp/knowledge-base/users/how-do-you-setup-roles.md).

# How do you setup roles?

1. Every new business comes with some default roles – Admin & Cashier
2. You can create a role by clicking on the Add button -> Giving a role name and then selecting the appropriate permission for that role.
3. Sometimes you may need to give a user access to some particular location(s) only. In this case, select the locations from “Access locations” permission. Select “All Locations” to give permission to access all locations for your business.
4. Role's permissions can be edited & deleted.

{% hint style="info" %}
**Settings:**

Admin has all permissions in the application.

Cashier has permission to only the POS section.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kbgfuzion.com/erp/knowledge-base/users/how-do-you-setup-roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
