> For the complete documentation index, see [llms.txt](https://docs.industryapps.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.industryapps.net/onboarding-to-industryapps/onboard-application/configure-application/access-rights.md).
# Access Rights
> "Shop floor requires multiple systems along the value chain. The most painful part is each system required different user management, role and access management."
>
> * Plant IT head
Role based access control is centrally managed in IndustryApps. This is to avoid customer having to manage various users and roles under each solution they subscribe to. Also this allows solution providers to not spend effort on creating complex user access management views.
Here you can provide what access roles you have covered in your solution ( Create, Edit, View, Delete...) Now these can be mapped here which customer can later assign to relevant users or roles which they have maintained centrally.
At least one access right should be enabled!
Click on Add Module
---
# 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.industryapps.net/onboarding-to-industryapps/onboard-application/configure-application/access-rights.md?ask=&goal=
```
`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.