> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/feature-reference/data-quality.md). # Action Center The Action Center surfaces actionable issues across your connected systems — data gaps, ownership problems, and configuration findings — so you can resolve them before they become risks. ![Action Center page showing four sections: Configuration (no issues), Sync (no issues), System (no issues), and Data — with five open items including activity data gaps, unmatched accounts, unowned service principals, machine identities with no inheritor, and empty groups; plus a USERS / PEOPLE section with individual user items](/files/K8WObPAZ00y4w8m0I4RH) *The Action Center groups issues by category. The Data section surfaces data quality issues — each with a severity badge (HIGH, MEDIUM, or LOW) and a direct action button. A separate Users / People section lists individual user-level findings.* ## What you can do here | Action | What it does | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Review **Configuration** section | Shows any setup or connection issues that need attention. | | Review **Sync** section | Shows any issues with recent Sync runs across your Connectors. | | Review **System** section | Shows any platform-level issues affecting AOH Sync. | | Review **Data** section | Shows data quality issues such as users with no activity data (MEDIUM), unmatched Accounts (HIGH), unowned enterprise applications (HIGH), Machine Identities with no technical inheritor (MEDIUM), and groups with no members (LOW). | | Review **Users / People** section | Lists individual user records with specific findings, such as no sign-in, lifecycle, or source-updated data on any linked account. | | Click **Open source systems** | Opens Source Systems so you can investigate why users have no activity data. | | Click **Resolve orphans** | Opens the Orphaned Accounts view to resolve Accounts with no matching Identity. | | Click **Review machine identities** | Opens the Machine Identities view to assign owners or technical inheritors. | | Click **Review access management** | Opens Access Management to address groups that have no members. | | Click **View accounts** | Opens the Accounts view for the specific user listed in the Users / People section. | | Click **×** on an issue | Dismisses that issue from the active list. | | Toggle **Show dismissed** | Reveals issues you have previously dismissed, so you can review or restore them. | ## How to use it {% stepper %} {% step %} **Open the Action Center** Click **Action Center** in the left navigation. The badge next to the label shows the current number of open issues. {% endstep %} {% step %} **Review each section** Work through Configuration, Sync, System, Data, and Users / People sections. Items with a **HIGH** badge should be addressed first. {% endstep %} {% step %} **Act or dismiss** Click the action button on each item (for example, **Resolve orphans**) to go directly to the relevant page, or click **×** to dismiss items you have already handled elsewhere. {% endstep %} {% endstepper %} ## How to investigate and resolve an issue Use the Action Center as a daily triage queue: work from HIGH to LOW severity, act on each item, then dismiss what you have handled. {% stepper %} {% step %} **Open the Action Center** Click **Action Center** in the left navigation. The badge next to the label shows the total number of open issues. {% endstep %} {% step %} **Identify the highest-severity items** Scan the DATA section for **HIGH** badges first — these represent the most urgent risks. The two HIGH items on a typical tenant are unmatched Accounts ("accounts matched to no person") and unowned service principals ("service principals have no owner"). **MEDIUM** items (no activity data, no technical inheritor) and **LOW** items (empty groups) can follow. {% endstep %} {% step %} **Open an item's detail view** Click the action button on the right side of the issue card to go directly to the relevant screen: | Issue | Action button | Where it takes you | | ---------------------------------------------- | ----------------------------- | ----------------------- | | Users with no activity data | **Open source systems** | Source Systems page | | Accounts matched to no person | **Resolve orphans** | Orphaned Accounts view | | Service principals with no owner | **Review machine identities** | Machine Identities view | | Machine identities with no technical inheritor | **Review machine identities** | Machine Identities view | | Groups with no members | **Review access management** | Access Management page | | {% endstep %} | | | {% step %} **Take the resolution action** On the destination screen, assign ownership, match the Account to an Identity, or remove the stale record as appropriate. Return to the Action Center once you have addressed the item. {% endstep %} {% step %} **Dismiss resolved or accepted items** Click **×** on an issue card to dismiss it from the active list. For the Users / People section, click **Dismiss all (21)** to clear all individual user findings at once. To review items you have dismissed, toggle **Show dismissed** in the top-right corner of the Action Center. {% endstep %} {% endstepper %} {% hint style="info" %} Dismissals are recorded in AOH Sync so you can always surface them again with **Show dismissed**. Dismissing an item does not fix the underlying data — it acknowledges that you have reviewed it. {% endhint %} ## Related * [Orphaned Accounts](/feature-reference/orphaned-accounts.md) * [Browsing Identities](/feature-reference/browsing-identities.md) * [Connectors](/feature-reference/connectors.md) * [How AOH Sync Works](/core-concepts/how-aohsync-works.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.aohwv.dev/feature-reference/data-quality.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.