> 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 RealmJoin Portal settings for customizing the portal and managing features, permissions, and Microsoft Azure resources. RealmJoin Portal settings allow administrators to customize their experience, manage RealmJoin features and interact with Microsoft Azure resources. ## Navigation ### General General settings for RealmJoin such as app deployment defaults, app configurations, user interface or Global Agent settings. ### Permissions Delegate different levels of permissions to users of the RealmJoin Portal (RBAC). ### Groups Configure group prefixes to descriptive names within the RealmJoin Portal. ### Log Analytics Connect Log Analytics Workspace to RealmJoin for in-depth logging. ### Workplace cloud storage Manage files within your cloud storage. ### RunBooks Connect Azure Automation to automate repetitive tasks with RunBooks. ### RunBook Customizations Customize parameters within existing RunBooks. ### RunBook Permissions Create granular access permissions for team members using RunBooks. ### Custom Roles Create additional RealmJoin Portal roles to catch use-cases that the standard permission roles are not covering. ### App Categories Create and manage Intune app categories. --- # 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=&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.