> ## Documentation Index
> Fetch the complete documentation index at: https://sync.bravastech.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# The Six Sync Types

> What each sync type changes, its default state, and its dependencies.

Bravas Sync processes six data categories independently. This keeps run history and exception handling specific to the data being changed.

| Sync type             | Purpose                                                                                             | Initial state | Depends on       |
| --------------------- | --------------------------------------------------------------------------------------------------- | ------------- | ---------------- |
| **Groups**            | Creates and maintains source teams, Tanda Departments, or Deputy Operational Units as Mitti groups. | Enabled       | None             |
| **Sites**             | Creates and maintains source locations or workplace Companies as Mitti sites.                       | Disabled      | None             |
| **Users**             | Creates and updates eligible people, email matching, active state, and seat type.                   | Enabled       | None             |
| **User Fields**       | Writes selected workforce details to Mitti built-in or custom profile fields.                       | Disabled      | Users            |
| **Group Memberships** | Aligns which synced users belong to which synced groups.                                            | Enabled       | Groups and Users |
| **Site Memberships**  | Aligns or seeds site access according to the selected mode.                                         | Disabled      | Sites and Users  |

Enabling a dependent sync also enables its prerequisites. A prerequisite cannot be turned off while an enabled sync still requires it.

## Provider Differences

<AccordionGroup>
  <Accordion title="Employment Hero">
    Groups and memberships come from teams. User Fields can use the complete supported field
    registry. Site Memberships default to **Initial primary only** with removal skipped when first
    enabled.
  </Accordion>

  <Accordion title="Tanda">
    Groups are Departments and Sites are Locations. Department membership comes from Department
    staff lists. Site Memberships can use every Department under a Location or each user's primary
    report department. Tanda exposes a narrower supported set of user fields.
  </Accordion>

  <Accordion title="Deputy">
    Groups are Operational Units. Group membership combines roster and management assignments. Sites
    come from active workplace Companies, and Site Memberships combine workplace rows with each
    user's primary Location. Only confirmed phone and date fields are offered in User Fields.
  </Accordion>
</AccordionGroup>

<Info>
  Sites and Site Memberships stay off until a site rollout is deliberately selected. Turning on a
  sync type can create, update, deactivate, or remove records according to its rules, so review the
  matching configuration page before saving.
</Info>