> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/introduction/user-roles-in-the-system.md). # User roles in the system ## User roles in the system The scope of actions available in the backend depends on the permissions assigned to the user. Permissions are usually grouped into roles that correspond to a position or area of responsibility. ### Typical business roles | Role | Example scope of work | | ----------------------------- | -------------------------------------------------------------------------------------------------- | | System administrator | Users, roles, permissions, dictionaries, locations and basic configuration. | | Product records administrator | Products, product groups, attributes, PLU codes, product images and business partner data. | | Price operator | Product prices, sales price lists, price imports and sales price updates. | | Promotion operator | Promotions, promotion baskets, coupons, loyalty cards and promotion conditions. | | Document operator | Orders, receipts, issues, invoices, related documents and document lists. | | Reporting user | Sales reports, stock reports, document reports and data export. | | Location manager | Reviewing documents and reports for a selected location, controlling stock levels and settlements. | ### Role and location A user works in the context of a selected location. This means that the same person may see different data after changing the work location. The location affects documents, warehouses, reports, product availability and selected operational processes. ### Role and permissions A role defines which system functions the user can view or modify. In practice, this may mean: * view-only access, * the ability to add new records, * the ability to edit existing records, * the ability to delete records, * the ability to confirm documents, * access to central or local reports. {% hint style="info" %} This documentation uses business role names to describe responsibilities more clearly. Actual role names in the system may be different because they are configured in `Administration -> System -> Roles`. {% 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.aquiladynamics.com/aquila-store-user-manual/introduction/user-roles-in-the-system.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.