> For the complete documentation index, see [llms.txt](https://cqube.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cqube.sunbird.org/use-cqube/additional-features/role-based-access-control.md).

# Role based access control

During the installation of cQube, three roles will be created within keycloak.

1. Private\_user
2. Guest (Default)
3. Admin

Any roles created will be associated with guest roles by default.

For accessing any private programs, users should be assigned private\_user.

Any user who needs access to the admin panel as well as the telemetry dashboard will have to be assigned the admin role. One can be assigned both private, guest, and admin roles, through which he will have access to every program within the dashboard.

During the installation, two users, one guest and an admin—will be created and assigned appropriate roles.

Any user once created can navigate to the role mapping tab, select the required role from the available roles list, and add it so it will be associated with the user.

<figure><img src="https://lh4.googleusercontent.com/z6XCSisn1IjfNV-gQVBvibYXT9J57LZV5uxR0hnXUq0P3liNkSBGyqRLIKNbGdILjyRZgysInmEOTcfit828tHlaM1S9NGk2BCryoYuOYkrHcMD7AUFKlAjhfwqGRZ-P8RccRTNVLT2UIkiccVH4_Y4" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh5.googleusercontent.com/Z_04Kpe_VxOkA_jMkyaQuhSWnN1K3b3L85jDKFn3Orwx7P8MAcAxC6psEaFTCYuzsUBkq21y1WR0k8SadivE1cIB6UFNZ7CgNZ7DRNFS3ASK8QdIL81de8Rlr-ShZqjuA2Tp6qYEW6J8KuvuLJz_xYk" alt=""><figcaption></figcaption></figure>


---

# 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://cqube.sunbird.org/use-cqube/additional-features/role-based-access-control.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.
