> 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/core-concepts/source-and-target-systems.md).

# Source & Target Systems

AOH Sync has two distinct types of systems: **Source Systems**, which supply identity data, and **Target Systems**, which receive it.

## Source Systems

A **Source System** is any system that holds authoritative identity data for your organization — typically an HR platform, a database-backed system, an API-connected system, or a flat-file feed.

AOH Sync reads from your Source Systems via **Connectors**. Each Connector is configured with the credentials, schedule, and field mappings needed to pull records from that source. You can connect multiple Source Systems simultaneously; AOH Sync merges the data they provide into a single normalized Identity for each person.

Supported source types include:

* HR platforms and payroll systems (via API or CSV/SFTP export)
* Database-backed HR and directory systems
* API-connected systems
* CSV and SFTP file feeds

You manage your Source Systems from the **Source Systems** screen under Configuration.

{% hint style="info" %}
AOH Sync never writes back to your Source Systems. It is read-only against every source you connect.
{% endhint %}

## Target Systems

A **Target System** is where AOH Sync provisions and manages accounts. Currently, AOH Sync provisions to **Microsoft Entra ID** (formerly Azure Active Directory).

Each Target System you configure represents one Entra ID tenant. AOH Sync uses a service principal — a non-interactive application identity you register in your Entra tenant during setup — to create, update, and disable user accounts on your behalf.

Within a Target System, AOH Sync can manage:

| Area             | What AOH Sync does                                                     |
| ---------------- | ---------------------------------------------------------------------- |
| **Directory**    | Creates and updates user accounts; disables accounts on deprovisioning |
| **Applications** | Assigns or removes application access based on group membership        |
| **Compliance**   | Reports on account state against your configured compliance posture    |
| **Security**     | Tracks sign-in risk, account status, and policy coverage               |
| **Helpdesk**     | Surfaces identity and account detail for support workflows             |

You manage your Target Systems from the **Target Systems** screen under Configuration.

## How they work together

```
Source System A  ──┐
Source System B  ──┼──►  AOH Sync  ──►  Target System (Entra ID tenant)
Source System C  ──┘
```

AOH Sync reads from all your Source Systems on each sync cycle, resolves any conflicts between them, and writes the authoritative result to your Target System. The Source Systems own the data; the Target System reflects it.

## Related

* [How AOH Sync Works](/core-concepts/how-aohsync-works.md)
* [Identities, Accounts & Users](/core-concepts/identities-accounts-users.md)
* [Connectors](/feature-reference/connectors.md)
* [Source Systems](/feature-reference/source-systems.md)
* [Target Systems (Entra)](/feature-reference/target-systems.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/core-concepts/source-and-target-systems.md?ask=<question>&goal=<endgoal>
```

`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.