The leaver is done on the effective date. Not sometime after.
nara runs joiners, movers, and leavers as one controlled process: details captured completely, plan approved by the owner, accounts and groups set on the effective date, every step in the ticket.
A joiner is not one ticket. It's fifteen.
Account, groups, licenses, hardware, access: a single HR event today spreads across inboxes, hallway requests, and half-finished checklists spanning HR, IT, and the business. On exit, it becomes a security risk: access that stays active too long only surfaces when someone goes looking. nara turns the event into one case with clear phases, one owner, and one effective date.
From HR event to documented result.
Capture
The agent captures the case completely: person, role, effective date, approver.
If something is missing, it asks instead of carrying a gap forward.
Plan
Knowledge and permissions turn into a concrete plan: which accounts, which groups, which steps.
The plan waits for the owner's approval.
Execute
After approval, the agent carries out the plan: enable or disable accounts, assign or revoke groups, directly in the directory service.
Anything nara cannot execute is documented cleanly for manual handling.
Prove
The agent verifies the result and closes the case with a complete timeline.
nara flags overdue deactivations on its own.
Control is not an add-on here. It is the process.
Approval before execution
No account is touched before the named owner has approved the plan.
Deadlines in view
A background monitor detects overdue offboarding deadlines and reports them in the ticket before an audit finds them.
The ticket as evidence
Every event runs as a case with status, history, and reasons. That is your audit trail, with no extra work.
Boundaries are defined
Steps outside the approved tools are not executed; nara hands them to your team, documented.
Frequently asked questions
Which systems does nara control here?
Today, Microsoft Entra ID: enabling and disabling accounts, managing group memberships. You connect any further system through your own typed tools, executed in the cloud or on your infrastructure.
How does a case reach nara?
Via chat, in Microsoft Teams, or from the ticket system. The agent captures the required fields per case type and creates the case with all details.
What about steps nara cannot execute?
They are documented in the case as open steps and handed to your team. Nothing disappears into a checklist.
Do we stay in charge?
Yes. The plan is approved before execution, critical actions require an additional confirmation, and every step is logged.
Show us your onboarding flow.
In the demo we rebuild one of your cases: from the report to the deactivated account, with approvals and a complete history.