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

# Connectors

The Connectors page is your central view of every active data bridge between AOH Sync and your Source and Target Systems.

![The Connectors list showing Identity Ingestion and Account Import groups, with the AOH Test AD connector card displaying sync progress](https://2706226485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8BF8xXbTZGWilkpjaGNh%2Fuploads%2Fgit-blob-6759990d5ee7380b3d05309c24948c0376c512d5%2Fconnectors-list.png?alt=media)

*The Connectors list groups your Connectors by type and surfaces live sync progress for each one.*

## What you can do here

| Action                                         | What it does                                                                                                        |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Filter by status (All, Active, Stopped, Error) | Narrows the list to Connectors in a specific state so you can quickly spot problems.                                |
| Search Connectors                              | Finds a specific Connector by name using the search field in the top-right corner.                                  |
| Run Now                                        | Triggers an immediate Sync for the selected Connector without waiting for the next scheduled run.                   |
| Logs                                           | Opens the Sync History view for the selected Connector, showing recent run results.                                 |
| Mappings                                       | Opens the Field Mappings tab for the selected Connector.                                                            |
| Click a Connector card                         | Opens the full Connector detail view with tabs for Overview, Mappings, MI Rules, Revisions, Schedule, and Settings. |

## Understanding the Connectors list

Connectors are grouped by type:

* **Identity Ingestion** — Connectors that pull Identities and Accounts into AOH Sync from your Target Systems (such as Entra ID or Active Directory). AOH Sync creates these automatically when you add a Target System.
* **Account Import** — Connectors that pull Accounts from your Source Systems into AOH Sync, linking them to existing Identities via the Connector's join key. AOH Sync creates these automatically when you add a Source System.

Each Connector card shows its current status (Running, Stopped, or Error), the time of its last Sync, the name of its Source System, and a live progress indicator when a Sync is actively running.

## Related

* [How AOH Sync Works](/core-concepts/how-aohsync-works.md)
* [Source & Target Systems](/core-concepts/source-and-target-systems.md)
* [Sync Types](/core-concepts/sync-types.md)
* [Connector Overview](/feature-reference/connectors/overview.md)
* [Field Mappings](/feature-reference/connectors/field-mappings.md)
* [Schedule](/feature-reference/connectors/schedule.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aohwv.dev/feature-reference/connectors.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.