Sector blueprint
IT services & GCCs
Roll a team from one client project to the next. Groups change, SCIM pushes the tools, and the audit shows exactly who had what.
Simulator IT services & GCCs
1 · Trigger an event
2 · Change the conditions
Ready. Pick an event.
Example event: Batch joins Falcon
- HR system project allocation
- AuthMantra groups + SCIM
- Group: Falcon client A project
- Group: Orion client B project
- Code host app
- Tickets app
- Cloud console app
- Client audit who had access
$ hr emit batch --project falcon --count 12 POST /scim/v2/Users x12 ✓ scim.user.created x12 in about 4 s ✓ app.assigned code-host, tickets (group: falcon) ✓ provisioning.pushed x12
- Batch joins Falcon new project starts
- Team rolls to Orion Falcon ends, Orion begins
- Client audit request who had Falcon access, Q3
- Engineer leaves mid-sprint resignation, last day today
All output on this page is simulated, with made-up names and values. Keys 1 to 4 run the events.
What you need
Projects as groups
One group per client project.
HR allocation feed
Sends moves by SCIM 2.0.
Tools with connectors
Code host, tickets, cloud console.
A rule for ending
Who removes the old group, and when.
Audit export habit
Run it per project at quarter end.
Try IT services & GCCs on your own people
Free for up to 10 people. Or book a consultation and we will walk through your setup.