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

# Source Systems

The Source Systems page is where you connect and manage the external data sources whose Account records AOH Sync imports into your Identity store.

## Where this data comes from

Source Systems are the authoritative records you own — HR platforms, collaboration tools, and other directories. AOH Sync reads Account data from each connected Source System on a schedule you control; it never writes back to your Source Systems.

![Source Systems page showing five connected systems — Bamboo, GitHub, Okta, Slack, and WorkDay — in two panels: an Account import panel where each system shows "Account import configured" and an "Ingestion configured" badge, and a GROUP Manual CSV panel listing the same five systems each with a "Manual CSV" badge and a chevron toggle](https://2706226485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8BF8xXbTZGWilkpjaGNh%2Fuploads%2Fgit-blob-eb9f4c43d699eecef7452f51e1d2e1c060e1038b%2Fsource-systems.png?alt=media)

*The Source Systems page shows two panels. The top **Account import** panel lists each system with its ingestion status. The lower **GROUP Manual CSV** panel groups the same systems by their data-delivery method; expand a row with the chevron toggle to see its connection details.*

## What you can do here

| Action                                         | What it does                                                                                           |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **+ Add Source System**                        | Opens the setup flow to connect a new Source System to AOH Sync.                                       |
| Expand a row in the **GROUP Manual CSV** panel | Click the chevron toggle on a system row to reveal its connection details and ingestion configuration. |
| Click a Source System name                     | Opens the detail view for that Source System where you can adjust settings.                            |

## Adding a Source System

Click **+ Add Source System** to open the setup flow. Choose the system type from the dropdown — available types include HR platforms (Gusto, ADP), relational databases (SQL Server, MySQL, and others), file feeds (CSV upload or CSV over SFTP), and LDAP directories. Supply the connection details for your chosen type and click **Save**. AOH Sync tests the connection and, if successful, adds the system to the list and automatically creates an Account Import connector for it.

For a step-by-step first-time walkthrough, see [Connect a Source System](/getting-started/07-connect-source-system.md).

## Related

* [Source & Target Systems](/core-concepts/source-and-target-systems.md)
* [Connectors](/feature-reference/connectors.md)
* [Field Mappings](/feature-reference/connectors/field-mappings.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 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/source-systems.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.