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

# General

General RealmJoin settings, including runbook sync, portal UI options such as the tenant banner logo, package automation defaults and update notifications.

## Runbook Sync

If you configure [Process Automation / Runbooks](https://docs.realmjoin.com/automation/runbooks.md) in your environment, you can click "Sync runbooks..." to update your runbooks from RealmJoin's public repository.

![](https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2Fz5nf9NPVzlUnzXuT1QMv%2Fimage.png?alt=media\&token=dea2e8b6-3dff-4717-85a6-b2a00a8427ba)

This will make sure, you have the current state of our runbooks, incl. bugfixes and new functionality. If needed, this will also install needed PowerShell modules in your Azure Automation Account.

## UI Config

The *UI Config* card holds tenant-wide display settings of RealmJoin Portal. They apply to every user of the tenant. Changing them requires the `CanChangeTenantSettings` permission.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2Fgit-blob-242c2d507c04888db275b97e1b20a5952863bc03%2Fsettings-general-ui-config.png?alt=media" alt="UI Config card"><figcaption><p>UI Config card</p></figcaption></figure>

### Show advanced info

Off by default. When enabled, the detail pages show the raw [data sources](https://docs.realmjoin.com/ugd-management/user-group-device-management.md#data-sources) as JSON, as icons or tabs on the right of the tab bar:

| Detail page                                                                       | Raw data views                                                       |
| --------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| [Device](https://docs.realmjoin.com/ugd-management/user-list/device-details.md)   | Entra ID Data, Intune Data, Autopilot Data, MDE Data, RealmJoin Data |
| [User](https://docs.realmjoin.com/ugd-management/user-list/user-details.md)       | Entra ID Data, Sign-In Data, RealmJoin Data                          |
| [Group](https://docs.realmjoin.com/ugd-management/user-list/group-details.md)     | Entra ID Data, RealmJoin                                             |
| Package                                                                           | Intune app, RealmJoin app and Package Store entry JSON               |
| [Organization](https://docs.realmjoin.com/ugd-management/organization-details.md) | Entra ID Data                                                        |

The tabs are only shown to users with the **Admin**, **Auditor** or **Advanced Supporter** role and to Entra ID Global Administrators. The underlying permissions are the `CanSee...Json` permissions and `CanSeeUserSignIns`, see [Available Permissions](https://docs.realmjoin.com/administration-and-settings/permission/custom-roles/available-permissions.md).

### Tenant banner logo

RealmJoin Portal can show your company logo in the toolbar at the top of every page and on the [Organization Details](https://docs.realmjoin.com/ugd-management/organization-details.md) page. Choose where the logo appears:

| Option                       | Toolbar | Organization page |
| ---------------------------- | ------- | ----------------- |
| Toolbar + Organization page  | ✓       | ✓                 |
| Toolbar only                 | ✓       | –                 |
| Organization page only       | –       | ✓                 |
| Toolbar only, white backdrop | ✓       | –                 |
| Both, white backdrop         | ✓       | ✓                 |
| No banner                    | –       | –                 |

*Toolbar + Organization page* is the default. The toolbar has a dark background. The two *white backdrop* options render the logo in the toolbar on a white background, for logos that are not readable on dark backgrounds. On the Organization Details page the logo is always shown without backdrop.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2Fgit-blob-737a418cfb267aa4e7b1c12557aa36bbef72410e%2Fsettings-general-banner-logo-both.png?alt=media" alt="Toolbar + Organization page: logo in the toolbar and on the Organization Details page"><figcaption><p>Toolbar + Organization page: logo in the toolbar and on the Organization Details page</p></figcaption></figure>

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2Fgit-blob-3b67dfc5d1fcb999a3c8c38e0a2114b8f110c632%2Fsettings-general-banner-logo-toolbar-white.png?alt=media" alt="Toolbar only, white backdrop: logo only in the toolbar, on a white background"><figcaption><p>Toolbar only, white backdrop: logo only in the toolbar, on a white background</p></figcaption></figure>

The logo is the **Banner logo** of the default sign-in experience in your tenant's [Entra ID company branding](https://learn.microsoft.com/en-us/entra/fundamentals/how-to-customize-branding). RealmJoin Portal reads it from Graph (`GET /organization/{tenantId}/branding/localizations/default/bannerLogo`) and does not store a copy. Banner logos of language-specific localizations are not used. To change the logo, upload a new banner logo in the Entra admin center under **Company branding**.

{% hint style="info" %}
If the default sign-in experience has no banner logo, no logo is shown and the previews on the card show a placeholder. RealmJoin Portal caches the logo for one hour, so a changed banner logo can take up to one hour to appear.
{% endhint %}

## Package Automation Defaults

If you source packages from RealmJoin's [Package Store](https://docs.realmjoin.com/application-management/packages/package-store.md), you can use [automation ](https://docs.realmjoin.com/application-management/packages/package-updates.md#automation)to keep these packages always up to date.

![Automation defaults for a package](https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FDhQHQdSFB6xbPZkJQyB6%2Fimage.png?alt=media\&token=18b9fc66-40e2-427e-b4a3-bf56658b8dc4)

The settings are:

* **AutoDeployMain** - Automatically deploy new versions of this package to your users. ("Main" subscription)
* **AutoDeployMainDeferInDays** - Wait for this number of days to pass before publishing a new version to "main". This is usefull to avoid stress for users/clients if multiple package versions are published rapidly.
* **AutoDeployPreview** - Automatically deploy new versions of this package to your pilot users. ("Preview" subscription)
* **AutoDeployPreviewDeferInDays** - Wait for this number of days to pass before publishing a new version to "preview".
* **AutoDeployAtNight** - Schedule automatic deployment during night time
* **Select target timezone** - If you use AutoDeployAtNight, use this Time Zone to indicate when "at night" is.

See [Package Updates and Automation](https://docs.realmjoin.com/application-management/packages/package-updates.md#automation) for more information on Package Automation.

## Group Naming Scheme

RealmJoin Portal can dynamically create and manage Entra groups for features like [package assignment](https://docs.realmjoin.com/application-management/packages/package-deployment.md) and [remediation script assignment](https://docs.realmjoin.com/automation/remediation-scripts.md#assignment).

### App / Package Deployment

RealmJoin can create assignment groups for Intune and RealmJoin Client packages. Use this to define the naming pattern the groups.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FY83K9kHGg76D0xOvTzLH%2Fimage.png?alt=media&amp;token=9b472c6c-7d3a-4978-a5ca-ba3b797f5db9" alt=""><figcaption><p>Package Deployment Group Naming Scheme</p></figcaption></figure>

You can use the following variables:

* **$vendor** - Name of the software vendor (if available)
* **$product** - Name of the software title
* **$appName** - Full name (vendor and product) of the software
* **$version** - Version of the package
* **$platform** - Platform of the package: `Win`, `macOS` or `Android`
* **$modifier** - either nothing, "available", "preview", "uninstall" or "update"
* **$groupName** - (only in description) Name of the Managed Group

If no template is set, RealmJoin uses `app - $platform - $appName ($modifier)`. Empty brackets are removed, so the Main group has no suffix.

### Remediation Scripts

If you use [RealmJoin managed Intune Remediation scripts](https://docs.realmjoin.com/automation/remediation-scripts.md#managed-scripts), you can define the naming scheme for [Managed Groups](https://docs.realmjoin.com/automation/remediation-scripts.md#managed-groups).

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FMvpEkzqw9qkw3hLOGzSV%2Fimage.png?alt=media&amp;token=6899800d-9227-4147-bc2f-44846a1ef399" alt=""><figcaption><p>Remediation Scripts Group Naming Scheme</p></figcaption></figure>

You can use the following variables:

* **$healthScriptName** - Name of the Managed Remediation Script
* **$modifier** - either "included" or "excluded" (Assignment vs. Exception)
* **$groupName** - (only in description) Name of the Managed Group

## Additional Update Notifications

For packages sourced from the [Package Store](https://docs.realmjoin.com/application-management/packages/package-store.md), the RealmJoin backend regularly compares the deployed versions with the Package Store and sends an email per package when its status changes:

* **New version available** - a newer version of the package was published in the Package Store.
* **Manual deployment** - an upgrade action (update Main, update Preview, create Preview or move Preview to Main) is available and has to be triggered manually.
* **Planned deployment** - [package automation](#package-automation-defaults) has scheduled an upgrade action. The email contains the action and the scheduled time.

The field **Send additional update notifications to …** on the *App Config* card takes email addresses that receive these emails for **every** package in the tenant. Separate multiple addresses with semicolons, e.g. `foo@example.com; bar@example.com`.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2Fgit-blob-e20e53bbeb10037a3a25adc72590f81b342f3282%2Fsettings-general-app-config.png?alt=media" alt="App Config card with an additional update notification recipient"><figcaption><p>App Config card with an additional update notification recipient</p></figcaption></figure>

This complements the [Technical Application Owners](https://docs.realmjoin.com/application-management/packages/package-settings.md#technical-application-owners) (TAO) of a package:

* **Technical Application Owners** are set per package and only receive notifications for that package, and only if notifications are enabled in the package's Config.
* **Additional update notification recipients** are set tenant-wide and receive the notifications for all packages, independent of the TAO settings.

{% hint style="info" %}
Invalid email addresses are dropped without an error when saving, so check the field after saving. The addresses are stored as a JSON array with a maximum length of 200 characters. For more recipients, use a distribution list.
{% endhint %}

## Managed App Priority Cascade

The *App Config* card also contains the tenant-wide switch **Classic priority cascade for managed apps**. It decides which assignment wins when a user or device is a member of both the Main (Required) and the Available group of a managed package:

* **Off** (default) - managed cascade: Available wins over Main (uninstall > update > preview > available > mandatory).
* **On** - classic cascade: Main wins over Available (uninstall > update > preview > mandatory > available).

Changing the switch asks for confirmation and takes effect immediately for every user and every managed package that has no per-package override. Individual packages can deviate from the tenant default via the *Priority cascade* setting in their [Expert Settings](https://docs.realmjoin.com/application-management/packages/package-settings.md#expert-settings).

See [Assignment priority and conflicts](https://docs.realmjoin.com/application-management/packages/package-deployment.md#assignment-priority-and-conflicts) for the full evaluation order, including Exclude and Uninstall.

## Client Configuration

With this tenant setting you can configure the timespan in which the RealmJoin Agent detects the primary user.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FPSwOyylVON6zGTUDF43f%2Fimage.png?alt=media&amp;token=b2d22859-0757-4b6f-b66f-ee6174609234" alt=""><figcaption></figcaption></figure>

## LAPS Configuration

With this tenant setting you can configure the expiration time of the RealmJoin LAPS Support Account.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FTYWiDOwpfJm9YhoVz3dT%2Fimage.png?alt=media&amp;token=88d25d9d-f4e2-404d-83c6-f1087b8962d8" 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://docs.realmjoin.com/administration-and-settings/general.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.
