Sector blueprint
Public sector
Strict roles and separated duties. Choose who is acting and see which requests succeed, which are refused, and what is recorded.
Simulator Public sector
1 · Trigger an event
2 · Change the conditions
Ready. Pick an event.
Example event: Try to change a role
- Department HR postings
- Person acting role you choose
- AuthMantra roles + policy
- Records app department files
- Admin console roles, apps
- Audit log append-only view
- Auditor view read only
- Mumbai region data at rest
$ Admin: change role target=dev.n role=it_admin ✓ login.success Admin ! stepup.required sensitive admin action ✓ stepup.success ✓ role.changed dev.n -> it_admin {"event":"role.changed","actor":"admin","target":"dev.n"}
- Try to change a role grant IT admin to Dev
- Try to export the trail all of September
- Officer is transferred to the Revenue wing
- IT admin assigns an app e-office to a team
- Officer retires superannuation date
All output on this page is simulated, with made-up names and values. Keys 1 to 5 run the events.
What you need
Role map
Who is admin, IT admin, auditor, member.
Cloud use permitted
Confirm your department may use India-hosted SaaS.
An HR or postings feed
Moves and exits by SCIM 2.0.
Admin passkeys
Step-up needs a fresh proof.
Your own counsel
Check procurement and data rules.
Data is hosted in Google Cloud Mumbai (asia-south1). Whether that suits your department is for your own counsel to confirm.
Try Public sector on your own people
Free for up to 10 people. Or book a consultation and we will walk through your setup.