For the complete documentation index, see llms.txt. This page is also available as Markdown.

Field Mappings

The Mappings tab lets you define how attributes from your Source System translate into AOH Sync's canonical Identity attributes before they are provisioned to your Target System.

Where this data comes from

Every field mapping starts with a raw attribute column from your Source System — for example, displayName or mail from an Active Directory source. AOH Sync reads these source columns during each Sync and transforms them into the canonical Identity attributes used across your environment. Mappings you define here never affect the original data in your Source System.

The Mappings tab for AOH Test AD → CloudSync (Delta), showing a table of Source Column to SCIM Attribute mappings with Active toggles and edit/delete actions

The Source Field Mappings table shows every attribute translation configured for this Connector, in priority order.

What you can do here

Action
What it does

Auto-Map Columns

Automatically creates mappings by matching Source System column names to known Identity attributes — a quick starting point for new Connectors.

Add Mapping

Opens a form to manually define a new source-to-Identity attribute mapping.

Edit a mapping (pencil icon)

Changes the source column, target Identity attribute, or priority for an existing mapping.

Delete a mapping (trash icon)

Permanently removes the mapping from this Connector.

Toggle Active switch

Enables or disables a single mapping without deleting it — useful for testing changes before they go live.

Understanding the mapping table

Each row in the Source Field Mappings table contains:

  • # — The priority order in which mappings are evaluated. Lower numbers run first.

  • Source Column — The raw attribute name as it appears in your Source System (for example, givenName, mail, accountEnabled).

  • SCIM Attribute — The canonical attribute identifier AOH Sync uses for this field (for example, first_name, email, status).

  • Active — Whether this mapping is included in the next Sync run.

  • Actions — Edit or delete the mapping.

How to use it

1

Review existing mappings

Open the Mappings tab and scan the table. Confirm that the Source Columns shown match the attributes your Source System actually exports and that the Identity attribute targets are correct.

2

Add or auto-map

Click Auto-Map Columns to let AOH Sync suggest mappings based on your source schema, or click Add Mapping to define one manually. Fill in the source column name, select the target Identity attribute, and set a priority number.

3

Enable or disable individual mappings

Use the Active toggle on each row to include or exclude a mapping from the Sync without deleting it. This is useful for safely testing a schema change.

4

Publish your changes

After saving edits, return to the Overview tab. If the unpublished changes badge is shown, publish your revision so the changes take effect on the next Sync run.

Unpublished mapping changes are tracked as a new revision. You can view and compare any published revision from the Revisions & History tab.

Last updated