Joiners and leavers handled once, not in five systems.
Version X holds employment records, onboarding and permissions in the same system as the work. One joining process grants access, assigns ownership and creates the first tasks; one leaving process reverses all of it. Available from the Scale tier.
Today
- Onboarding is a checklist run across five separate admin panels.
- Someone leaves and their accounts stay assigned to them for a month.
- Permissions drift, because they are configured separately everywhere.
On Version X
- One process across every module, because there is one system.
- Departures reassign accounts, deals and open work as part of leaving.
- Role tiers defined once and applied everywhere.
Who does this work
Not a tool you operate. Ori orchestrates, and the heads below do the work on your desk.
Head of Knowledge
Answers from your actual process rather than a general model, and says when the documentation and the records have drifted apart.
Head of People
Holds employment records, onboarding and permissions on the same graph as the work itself.
Head of Legal
Drafts from the record that produced the deal, and checks the clauses before anyone signs.
Meet the rest of the team, and add specialists of your own wherever you need them.
The modules you will live in
Questions.
Which tier includes People?
Scale and Suite. It is absent from Launch on the basis that formal HR process is one of the things a five-person team genuinely does not need yet.
Does it do payroll?
No. Employment records, onboarding, offboarding and permissions. Payroll stays where it is.