Implementation guide
Roles and policy first. Workflows second.
Every organisation goes live in the same order: decide who can do what before anyone uses it for real work.
- 1
Roles
Define who holds which role — employee, manager, HR admin, finance approver — before any request runs live. Roles start from a template per team, not a blank slate.
- 2
Policies
Configure the rules a request is checked against: leave policy, spend limits, approval thresholds and escalation paths. Set once, enforced the same way in chat and in the app.
- 3
Access
Map permissions to roles — who can see which records and who can approve what — so access matches your organisation, not a generic default.
- 4
Integrations
Connect single sign-on (OIDC), SCIM, TallyPrime and anything else in scope. The integrations catalogue says exactly what each connector reads, writes and needs.
- 5
Go live
Only then do people start filing real requests. This order keeps the first real request from hitting an unconfigured policy.
One team first, or everyone at once?
Both work. Most organisations pilot with one team — commonly HR or IT — set up roles and policy for that team, then add apps as each team is ready. Organisations confident in their policies can roll out company-wide from the start. We help you choose on the discovery call.
Scope your rollout with us.
A 30-minute call scoped to your teams, your policies and your integrations — not a generic tour.