> 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/settings.md).

# Settings Overview

Overview of the RealmJoin Portal settings tabs, what each tab configures, who can see it, and where to find the detailed documentation.

The **Settings** page in the RealmJoin Portal holds the tenant-wide configuration: Portal roles, defaults for the RealmJoin Agent and for package deployment, and the connections to Azure resources (Azure Automation, Log Analytics, Azure Storage).

Each area of the settings lives on its own tab. The sections below describe the tabs in the order the Portal shows them and link to the page that covers each one in detail.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2Fgit-blob-e3ec6ca7684c701e8f422876d58aeee69fdd7724%2Fsettings-tabs.png?alt=media" alt="Tab bar of the Settings page in the RealmJoin Portal"><figcaption><p>Settings tabs</p></figcaption></figure>

{% hint style="info" %}
Viewing the settings requires the `CanReadSettingsDetails` permission, changing them requires `CanChangeTenantSettings` (see [Available Permissions](https://docs.realmjoin.com/administration-and-settings/permission/custom-roles/available-permissions.md)). Some tabs only appear when the matching feature is enabled for your tenant or when you hold a specific permission. Each section below names that condition.
{% endhint %}

## General

Tenant-wide defaults that do not need a tab of their own, grouped in cards:

* **Runbook**: sync your runbooks with RealmJoin's public repository.
* **UI Config**: change the Portal's appearance for all users, for example the tenant banner logo.
* **Client Configuration**: the timespan in which the RealmJoin Agent detects a device's primary user.
* **LAPS Configuration**: the expiration time of the RealmJoin LAPS support account.
* **App and remediation script deployment**: the group naming scheme RealmJoin uses when it creates assignment groups.
* **Package automation defaults**: whether and when new versions of Package Store packages are deployed automatically.
* **Multi Admin Approval**: email notifications for runbooks that need a second administrator's approval. Only shown with `CanChangeTenantSettings`.

Learn more: [General](https://docs.realmjoin.com/administration-and-settings/general.md)

## Permissions

Delegate access to the RealmJoin Portal by assigning Entra ID groups to RealmJoin roles (role-based access control). The tab lists each role together with the Entra ID groups assigned to it.

Learn more: [Roles and Permissions](https://docs.realmjoin.com/administration-and-settings/permission.md), [Pre-defined Roles](https://docs.realmjoin.com/administration-and-settings/permission/pre-defined-roles.md)

## Groups

Define the group name prefixes RealmJoin uses (for example `app` for application assignment groups) and map them to descriptive titles. RealmJoin shows these titles when it refers to the groups. The groups themselves are not renamed.

Learn more: [Group Namespaces](https://docs.realmjoin.com/administration-and-settings/groups.md)

## Client Config

The tenant-wide base configuration for the RealmJoin Agent, edited as key/value pairs. These settings have the lowest priority: anything assigned to the "RealmJoin - All Users" group, to a group or to a user overrides them.

Only shown with the `CanChangeTenantSettings` permission.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FnzKkAX4g78L5NiagLQkl%2F26-06-10-08_41_29_msedge.png?alt=media&amp;token=ac32da06-2cd1-45d2-843d-99d1e852d055" alt="Client Config tab with the tenant-wide key/value configuration"><figcaption><p>Client Config tab</p></figcaption></figure>

Learn more: [Tenant Default Values](https://docs.realmjoin.com/ugd-management/user-and-group-settings.md#tenant-default-values), [Available RealmJoin Policies](https://docs.realmjoin.com/ugd-management/user-and-group-settings/additional-settings.md)

## Log Analytics

The Log Analytics workspace RealmJoin writes its logs to. The tab shows the current connection, the setup command for the RealmJoin PowerShell module and, when the deployed schema is outdated, the command to update it.

Learn more: [Connecting Azure Log Analytics Workspace](https://docs.realmjoin.com/monitoring-and-logs/log-analytics.md), [Migrating to the Log Ingestion API](https://docs.realmjoin.com/monitoring-and-logs/log-ingestion-api-migration.md)

## Workplace cloud storage

The connection string of the Azure Storage account behind Workplace Cloud Storage. Use **Reset setup** to run the configuration wizard again.

Only shown when Workplace Cloud Storage is enabled for your tenant.

Learn more: [Workplace Cloud Storage](https://docs.realmjoin.com/administration-and-settings/workplace-cloud-storage.md)

## Runbooks

The Azure Automation account RealmJoin runs runbooks in: tenant, subscription, resource group, automation account, location, the runbook branch to sync and an optional Hybrid Worker group.

Learn more: [Connecting Azure Automation](https://docs.realmjoin.com/automation/connecting-azure-automation.md), [Runbooks](https://docs.realmjoin.com/automation/runbooks.md)

## Runbook Customizations

A JSON editor to adjust existing runbooks for your tenant: tenant-specific parameters and templates, user pickers or dropdowns, readable parameter descriptions, and hidden UI elements. Settings here override the defaults in the runbook itself.

Learn more: [Runbook Customization](https://docs.realmjoin.com/automation/runbooks/runbook-customization.md)

## Runbook Permissions

A JSON editor to control which users see which runbooks, and to hide runbooks for everyone.

Learn more: [Runbook Permissions](https://docs.realmjoin.com/automation/runbooks/runbook-permissions.md)

## Custom Roles

A JSON editor to define additional RealmJoin Portal roles from individual permissions, in addition to the pre-defined roles.

Only shown when Custom Roles are enabled for your tenant.

Learn more: [Custom Roles](https://docs.realmjoin.com/administration-and-settings/permission/custom-roles.md), [Available Permissions](https://docs.realmjoin.com/administration-and-settings/permission/custom-roles/available-permissions.md)

## MCP Access

Create and revoke the access tokens MCP clients use to connect to the RealmJoin MCP server. The tab lists all tokens of the tenant with owner, status, expiry and last use. A new token is shown once after creation.

Only shown to users with the RealmJoin Admin role or the Entra ID Global Administrator role (Portal policy `CanAdministerOwnTenant`, not assignable through custom roles), and only when the MCP server is enabled for your tenant.

Learn more: [MCP Server](https://docs.realmjoin.com/dev-reference/mcp-server.md)

## App Categories

The tenant's list of app categories. A RealmJoin package uses one of them as its group name in the RealmJoin Tray, an Intune app can have several as Intune app categories. Add, rename and delete categories here.

Only shown with the `CanReadAppCategories` permission. Editing requires `CanEditAppCategories`.

Learn more: [App Categories](https://docs.realmjoin.com/administration-and-settings/app-categories.md)


---

# 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/settings.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.
