Source · HR and payroll
The people record. Start dates, terminations, teams and custom employee fields.
- Users
- Groups
- User Fields
- Group Memberships
- Sites
- Site Memberships
HR to Mitti · a Bravas product
Your roster lives in HR.
Mitti should listen.
Bravas Sync keeps Mitti in step with Employment Hero, Tanda and Deputy. Users, groups, memberships, sites and custom fields, synced hourly with audit trails and exceptions surfaced for review.
Overview
What is in sync right now, and what changed on the last run.
Users synced
128
128 total
Groups synced
14
14 total
Integrations
2/2
6 sync configs enabled
Last sync
1h ago
Completed
Last run
UsersPending
Connect
Scan
Compare
Process
Cleanup
Integrations
Connected
ConnectedRecent activity
Groups, UsersNo changes8.7s1h agoGroups, Users2 Added
9.1s2h agoGroups, Users1 Removed
8.3s3h ago6
Sync types
3
HR sources
Hourly
Default cycle
0
CSV imports
01 — Why
Stop pasting names into spreadsheets at 8am on a Monday.
You hired ops people to think, not to chase. Bravas Sync is the missing layer between the system of record your business already maintains, HR, and the system your front line actually uses, Mitti.
Without
- Quarterly bulk CSV imports
- Stale group memberships
- Manual user deactivations
- No audit trail when things break
With Bravas Sync
- Hourly continuous sync
- Pattern-matched group rules
- Staged provisioning and auto-disable
- A diff for every change
02 — Sources
Three sources.
One destination.
Each platform is connected with its own credential and speaks its own vocabulary. Bravas Sync maps it onto Mitti's.
Source · Workforce operations
Rosters and time. Departments become groups, locations become sites.
- Users
- Departments
- User Fields
- Department Memberships
- Locations
- Location Memberships
Source · Workforce management
Scheduling and areas. Operational units become groups, locations become sites.
- Users
- Operational Units
- User Fields
- Unit Memberships
- Locations
- Location Memberships
Destination · Operations platform
Users, groups, sites, memberships and custom fields land here, through the Mitti API, with a diff recorded for each change.
Something else?
Your HR platform,
named here.
Tell us what it talks to
03 — Product
A day inside
the platform.
Three moments from the dashboard your operations team works in: a run landing, an exception being resolved, a credential being renewed.
01 · Runs
See every change land.
Each cycle records a run per sync type: status, counts, duration and the phases it went through. Open any run for the full diff.
Run history
| Type | Status | Summary | ||
|---|---|---|---|---|
| Users | Completed | Scheduled | 3 Added1 Updated124 Unchanged | 5.2s |
| Groups | Completed | Scheduled | 1 Out of Sync11 Unchanged2 Skipped | 3.5s |
| Sites | Failed | Manual | 8 Unchanged1 Failed | 2.9s |
| User Fields | Completed | Scheduled | 118 Updated10 Unchanged | 21.4s |
| Group Memberships | Completed | Scheduled | 9 Added2 Removed201 Unchanged | 7.1s |
5 runs loaded
Run detail
SitesFailed
8 Unchanged1 Failed
- Trigger
- Manual
- Duration
- 2.9s
- Started
- 9 Sept 2026, 09:00
- Items
- 9
Connect30ms
Scan2.2s
Compare45ms
Process600ms
This sync item could not be completed. Review the affected record and integration connection, then retry the sync. Contact Bravas if the issue persists.
02 · Review items
Exceptions in view.
Exceptions surface as review items with a likely cause and a recommended action, so operators can investigate while scheduled syncs continue.
3 review items waiting
1error2warningsReview the cause and recommended action for each exception.
ErrorOpenp.nair@example.comEmployment Hero · Users
Email update blocked
Last seen 2h ago3 occurrences
Likely cause
Mitti already has a different user with this email address.
Recommended action
Decide which record should own the email, then rerun Users.
WarningOpenNorth DepotDeputy · Sites
Site name mismatch
Last seen 3h ago1 occurrence
WarningOpenFront of HouseTanda · Groups
Group name mismatch
Last seen 1d ago1 occurrence
03 · Integrations
Connect once. Stay healthy.
OAuth or API key per provider. Token health sits on the integration card, and an expiring token is loud rather than silent.
Connected
Connected
Sync types
Six sync types, scoped per client.
Toggle them per provider. Apply staged provisioning, include patterns and field skip flags without touching code.
- 01UsersCreate, update and deactivate Mitti users from the HR record.
- 02GroupsMirror HR teams to Mitti groups, with include patterns and dual-group mode.
- 03User fieldsWrite custom field values per user through a per-client field mapping.
- 04MembershipsKeep group membership in step as people move between teams.
- 05SitesBring locations across as Mitti sites where the source supports them.
- 06Site membershipsPlace users at their primary site, with rules for what happens after.
04 — How it works
Three weeks of setup,
then it just runs.
Most clients are syncing real data within the first session. Scope grows as the sync rules mature.
Connect
OAuth or API key per provider, per client. Credentials are encrypted at rest.
Map
Pick the sync types, set the group rules, point custom fields at Mitti field ids.
Run
Hourly schedules, on-demand reruns, exception review. Mitti catches up to HR.
05 — Security
Credentials encrypted. Changes accountable. Access scoped.
We touch your most sensitive system of record. We treat it like it.
AES-256-GCMToken rotationFull audit trail
- 01Encrypted at restAES-256-GCM for every credential. Mitti passwords are never stored.
- 02Full audit trailEvery diff is recorded: who, what, when, and the prior value.
- 03Scheduled or on demandHourly cycles by default. Manual reruns when you need them.
- 04Role-based accessOperators run syncs, admins manage connections, viewers read.
06 — FAQ
Questions ops teams actually ask.
01What does Bravas Sync actually sync?
Groups, users, user fields, memberships, sites and site memberships. Employment Hero handles people. Tanda and Deputy add sites and rosters. Mitti is always the destination.
02How fresh is the data?
The sync engine runs hourly by default. You can trigger an on-demand cycle from the dashboard or scope a rerun to a single sync type.
03What happens when something looks wrong?
Conflicts and missing references surface as review items with guidance for investigation. Scheduled syncs continue, and some failures are retried automatically.
04Can I run multiple HR sources for one client?
Yes. Scheduling and sessions are scoped per integration, client plus source provider, so you can layer Employment Hero with Tanda or Deputy for the same workspace.
Ready when you are
Skip the spreadsheet.
Sync the source.
Set up a sandbox for your team in under an hour. Connect one provider, run one sync, and decide if it earns a place in your stack.