> 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/getting-started/07-connect-source-system.md).

# Step 6 — Connect a Source System

Connect the HR or identity system that AOH Sync reads people from. Adding a Source System automatically creates an Account Import connector for it. (\~5 minutes)

{% stepper %}
{% step %}
**Open Source Systems and add a new source**

Navigate to **Source Systems** in the left sidebar. Click **+ Add Source System** and choose the system type from the dropdown.

![Add Source System dialog showing a type-selection dropdown with options including HR platforms, relational databases, file feeds, and LDAP directories](/files/TEzhIylUP5pYm7kQ9NW9)

*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.*
{% endstep %}

{% step %}
**Enter the connection details**

After selecting your source type, the form expands with fields specific to that type. Supply the required details:

* **HR platforms (Gusto, ADP)** — enter your API credentials.
* **Relational databases (SQL Server, MySQL, and others)** — complete the connection form with your host, port, credentials, and database details.
* **File feeds (CSV)** — for CSV over SFTP, enter the SFTP host and path; for a direct CSV upload, use the **Download Template** option to get a correctly structured file, then upload it.
* **LDAP** — enter the directory server host, bind credentials, and base DN.

![Source System connection form showing the SQL Server example — fields for System Name, Database driver (fixed per type), Database host, Database port, Database username, and Database password](/files/XUp3c2wL3nBnNiYD0aW1)

*The connection form shown here is for a SQL Server source. Fields vary by type; CSV types show a Download Template option and a file upload control instead.*
{% endstep %}

{% step %}
**Save and confirm the Account Import connector**

Click **Save**. AOH Sync tests the connection and adds the new Source System to the list. At the same time, AOH Sync automatically creates an **Account Import connector** for it — this connector is responsible for bringing Account records from the source into AOH Sync and linking them to Identities by a join key.

![Connectors page showing a newly created Account Import connector for the connected source system](/files/ENbjG2QCgCtXsU3nRXpn)

*Each connected Source System gets its own Account Import connector. You can see it on the Connectors page immediately after saving.*
{% endstep %}
{% endstepper %}

## How to check it worked

The new source appears in the **Source Systems** list, and an **Account Import** connector for it appears on the **Connectors** page.

## Related

* [Step 7 — Connect a Target System](/getting-started/08-connect-target-system.md)
* [Source Systems](/feature-reference/source-systems.md)
* [Connectors](/feature-reference/connectors.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/getting-started/07-connect-source-system.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.