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.
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.- Employment Hero
- Tanda
- Deputy
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.
- Site access default: Initial Primary Only adds first access; ongoing access stays managed in Mitti.
- Profile fields: Employment Hero’s available fields, including its supported emergency-contact fields.
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.
Shared Settings: Start With the Outcome
Decide Which Groups and People Belong in Mitti
Use Groups to choose source groups by name and control their destination names. Use 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 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 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 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.
- 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.
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.
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.
Safe Change Pattern
- Confirm the active organization and provider.
- Record the current setting and expected outcome.
- Change one related rule set at a time.
- Save, then inspect the next run and Review Items.
- If the outcome differs from the expectation, avoid repeated retries and contact Bravas with the run time and non-sensitive record identifier.