Skip to main content

​
Integration Schedule

Shared by Employment Hero, Tanda, and Deputy. One schedule applies to every enabled sync type for the selected source integration. It is not a separate schedule for each rule or person.

​
Mode

Default: Scheduled. Choices: Scheduled or Manual.
  • Scheduled: Runs automatically at the daily times you choose.
  • Manual: Runs when an administrator uses Run Sync instead of starting at the saved daily times.
Use Manual when runs should require an operator’s decision. Switching to Manual preserves the saved times for later, but does not cancel a run that has already started.

​
Daily Run Times

Default: 12:00 AM. Choices: One to 24 different whole hours per day. Select the local hours when this integration should run. For example, 8:00 AM and 4:00 PM create two daily run slots in the organization’s timezone. At least one time is required in Scheduled mode. Choose times that fit when your source records are ready. Adding a time schedules another run of the enabled sync types; it does not change which records are eligible.

​
Organization Timezone

Where to change it: Organization Settings, not the integration schedule panel. Fallback when unset: Australia/Sydney. This determines how the platform interprets scheduled hours and daily-report windows. Use the organization’s operating timezone, not necessarily the timezone of the person configuring the integration. A change applies beyond this one integration, so review both schedules and reporting expectations first.

​
Pause Automatic Syncs

Where to change it: Organization Settings. Use the organization-wide pause when all automatic syncs should stop starting, rather than changing each integration to Manual. Manual triggers still work while automatic syncs are paused.
Scheduled times are local to the organization. Daylight-saving changes follow the configured timezone rather than a fixed UTC hour.

​
Exclusion Groups

Shared by all three providers. Use an exclusion when a source group and its people should intentionally stay outside the normal sync. Source groups are Employment Hero teams, Tanda Departments, or Deputy Operational Units. The integration panel lists source groups that should be skipped. A built-in group named Exclude from SC is always described in the interface. That is the exact group name, even though the destination platform is now called Mitti.
  • Add an exclusion: Choose the source group that should be left out.
  • Reason: Optionally explain why it is excluded so the next administrator understands the decision.
  • Disable an exclusion: Keep the entry but stop applying it.
  • Remove an exclusion: Delete that exclusion entry; this does not delete the source group.
An active exclusion prevents that source group and its related group-membership processing from being applied normally. Users who belong to an actively excluded group, including Exclude from SC, are also skipped by Users. This applies even when Require group membership is off or the person also belongs to another synced group.

​
Safe Example

For a synthetic source group named Training Sandbox, add it as an exclusion with the reason Non-production training records. Save the exclusion, then verify the next Groups, Users, and Group Memberships runs. Confirm that the group’s members are skipped by Users, including anyone who also belongs to another synced group, and that excluded groups and memberships are not created or assigned.
Removing or disabling an exclusion makes the source group eligible again. Review include patterns and membership rules before doing so.
User and site exclusions are not exposed as general client controls. Ask Bravas if the required outcome cannot be represented by the group exclusion interface.