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

# Configuration Overview

> Choose your integration, understand its settings, and know what will change in Mitti.

Open **Integrations**, select a connected source provider, and expand a sync type to view its rules. Changes remain pending until you choose **Save**.

<Info>
  Organization administrators can save exposed integration settings. Members can inspect the
  organization data available to their role, but configuration mutations require administrator
  access. Availability can also depend on the organization's rollout.
</Info>

## Choose Your Integration

The same sync has different names in each source platform. Start with your provider, then follow the shared settings below. A **provider-specific** section only applies to the provider named in its heading.

<Tabs>
  <Tab title="Employment Hero">
    Teams become Mitti groups. Locations provide the source for sites in an approved site rollout.

    * **Provider-specific user rules:** [Start Date Offset, Email Priority, and the current Staged Provisioning flow](/docs/configuration/users#employment-hero-only).
    * **Site access default:** [Initial Primary Only](/docs/configuration/sites-and-memberships#initial-primary-only) adds first access; ongoing access stays managed in Mitti.
    * **Profile fields:** [Employment Hero's available fields](/docs/configuration/user-fields#employment-hero), including its supported emergency-contact fields.
  </Tab>

  <Tab title="Tanda">
    Departments become Mitti groups. Locations become Mitti sites. The integration panel calls their memberships **Department Memberships** and **Location Memberships**.

    * **Unique group rules:** [Team Group Allowlist and Require Team Group](/docs/configuration/groups#tanda-only).
    * **Unique site rule:** [Location Source](/docs/configuration/sites-and-memberships#tanda-only) chooses all Department memberships or the primary report Department.
    * **Site access default:** Mirror Source, with removal allowed once this sync type is enabled.
    * **Profile fields:** [Tanda's available fields](/docs/configuration/user-fields#tanda).
    * **Not supported by the current flow:** Employment Hero's early-start filtering and staged provisioning, even if those controls appear in the panel.
  </Tab>

  <Tab title="Deputy">
    Operational Units, the roster areas within a location, become Mitti groups. Active workplace Companies become Mitti sites. The panel uses **Operational Unit Memberships** and **Location Memberships**.

    * **No Deputy-only rule controls** are currently exposed. Use the shared group, user, and site-membership rules. Do not use the Employment Hero-only early-start or staged-provisioning settings.
    * **Site access source:** Workplace assignments and each employee's primary Location.
    * **Site access default:** Mirror Source, with removal allowed once this sync type is enabled.
    * **Profile fields:** [Confirmed phone and date fields only](/docs/configuration/user-fields#deputy). Job title and emergency-contact fields are not available.
  </Tab>
</Tabs>

<Note>
  Sites, Site Memberships, and User Fields start disabled for every provider. A default describes
  the starting configuration, not necessarily your organization's saved settings. Check the panel
  before making a change.
</Note>

## Shared Settings: Start With the Outcome

### Decide Which Groups and People Belong in Mitti

Use [Groups](/docs/configuration/groups) to choose source groups by name and control their destination names. Use [Users](/docs/configuration/users) to choose who is eligible, what seat they receive, and whether inactive people are deactivated.

**Group Memberships** assigns people to the synced groups. It has an enable switch, not a separate general rule editor. It requires both Groups and Users.

### Choose Which Profile Details to Keep Updated

Use [User Fields](/docs/configuration/user-fields) for optional phone, date, job, and emergency-contact details supported by your provider. First name, last name, and email belong to Users instead.

### Decide Who Controls Site Access

Use [Sites and Memberships](/docs/configuration/sites-and-memberships) to choose whether the source controls ongoing access, only adds access, or seeds a person's first site. These choices are separate from group membership.

### Set Timing and Exceptions

Use [Schedules and Exclusions](/docs/configuration/schedules-and-exclusions) to choose run times and deliberately leave source groups and their members out of the sync.

## Settings Outside the Rule Editor

* **Connections:** Connect, reconnect, or disconnect a provider from its integration panel. See [Connect Providers](/docs/integrations/providers).
* **Organization Settings:** Set the timezone or pause automatic syncs for the organization. A timezone change affects both schedules and report windows.
* **Daily Reports:** Enable daily reports and set primary and CC recipients in Settings. See [Daily Sync Report](/docs/operations/reports).

## Bravas-Managed Settings

These settings are not general client controls even when their effect appears in the dashboard:

* the organization's default Mitti seat type;
* which source providers are allowed for the organization;
* source-to-Mitti record IDs, user-field IDs, and other mappings;
* workforce-access policy and tenant identity binding;
* site assignment lead days for staged provisioning;
* provider application registration, scopes, encrypted credential storage, and runtime limits; and
* migrations, scheduled-job infrastructure, Slack report routing, and diagnostic infrastructure.

Ask Bravas to change a managed setting. Include the intended outcome and organization, but do not send credentials or exported employee data.

## Save Behavior and Dependencies

* Enabling **User Fields** also enables **Users**.
* Enabling **Group Memberships** also enables **Groups** and **Users**.
* Enabling **Site Memberships** also enables **Sites** and **Users**.
* A prerequisite stays locked while an enabled dependent sync requires it.
* **Discard** clears pending changes in the open panel. It does not undo previously saved changes.

<Warning>
  Treat deletion, deactivation, removal, and mirror settings as outcome-changing controls. Confirm
  the source is authoritative and review the next run after saving.
</Warning>

## Safe Change Pattern

1. Confirm the active organization and provider.
2. Record the current setting and expected outcome.
3. Change one related rule set at a time.
4. Save, then inspect the next run and Review Items.
5. If the outcome differs from the expectation, avoid repeated retries and contact Bravas with the run time and non-sensitive record identifier.