> 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/ugd-management/organization-details.md).

# Organization Details

RealmJoin organization details show an Azure tenant overview: user and group counts, Intune and runbook stats, and recent app changes.

![Organization Details View](https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2F7lyChiidO1nwewbK1EqT%2F2022-02-07%20RJ%20ORG.png?alt=media\&token=4a795446-50f8-4c21-879e-c25eb3729481)

This page gives you an overview about

* Your organization (Azure Tenant), including number of users and groups
* Intune and Runbook Statistics
* The status of RealmJoin's features and integration
* Recent application updates and changes

This page follows the same principles as the other details pages. You have core properties of your tenant visible on the left side of the UI. The right side is specific to your current tab, which can include [runbooks](/ugd-management/user-group-device-management.md#runbooks) and [Entra ID raw data](/ugd-management/user-group-device-management.md#data-sources).


---

# 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/ugd-management/organization-details.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.