# General
## Runbook Sync
If you configure [Process Automation / Runbooks](/automation/runbooks.md) in your environment, you can click "Sync runbooks..." to update your runbooks from RealmJoin's public repository.
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.
## Package Automation Defaults
If you source packages from RealmJoin's [Package Store](/app-management/packages/package-store.md), you can use [automation ](/app-management/packages/package-details.md#automation)to keep these packages always up to date.
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 Details](/app-management/packages/package-details.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](/app-management/packages/package-details.md#assignments) and [remediation script assignment](/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.
Package Deployment Group Naming Scheme
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
* **$modifier** - either nothing, "available", "preview" or "uninstall"
* **$groupName** - (only in description) Name of the Managed Group
### Remediation Scripts
If you use [RealmJoin managed Intune Remediation scripts](/automation/remediation-scripts.md#managed-scripts), you can define the naming scheme for [Managed Groups](/automation/remediation-scripts.md#managed-groups).
Remediation Scripts Group Naming Scheme
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
## Client Configuration
With this tenant setting you can configure the timespan in which the RealmJoin Agent detects the primary user.
## LAPS Configuration
With this tenant setting you can configure the expiration time of the RealmJoin LAPS Support Account.
---
# Agent Instructions: 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:
```
GET https://docs.realmjoin.com/realmjoin-settings/general.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.