> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/administration-and-settings/permission.md).

# Roles and Permissions

Delegate RealmJoin Portal access to Entra users with pre-defined roles or flexible custom roles.

## Architecture

You can delegate access to different levels of functionality of RealmJoin Portal to **Entra users** via **pre-defined and/or custom roles:**

* **pre-defined roles** with a **fixed set of permissions**
  * **recommended** and **ready-to-use**
  * multiple roles can be combined although this increases complexity (not recommended)
  * assignable to Entra groups
  * see [available roles](/administration-and-settings/permission/pre-defined-roles.md)
* **custom roles** with **flexible** selection of **permissions**
  * if pre-defined roles do not meet your requirements, you can **request** [**Custom Roles**](/administration-and-settings/permission/custom-roles.md) to be enabled for your environment
  * custom roles can be combined with pre-defined roles (to add additional permissions) although this increases complexity (not recommended)
  * assignable to Entra groups and/or single users

To delegate/limit which subset of runbooks can be used by different operators, please see [Runbook Permissions](/automation/runbooks/runbook-permissions.md).

### Permission Defaults

By default, all users will have access to the [User profile](/ugd-management/user-profile.md) page to facilitate self-service scenarios.

During initial onboarding, the Entra role "Global Administrators" is also assigned as a RealmJoin Administrator to facilitate the initial configuration process.


---

# 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.realmjoin.com/administration-and-settings/permission.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.