Joiners and leavers, handled the same way every time
One form starts it. Accounts, licences, group membership and kit requests are created in order, approvals are asked for where policy requires them, and on the last day access goes away the same day.
- Best for
- IT and people teams
- Deployment
- Cloud or self-hosted
- Works with
- Google, Microsoft, Slack, GitLab, GitHub
The checklist only works when somebody remembers it
Starters and leavers are handled by a document that lives in a shared drive, executed by whoever is free, in whatever order they get to it.
- A new starter waits on their second day because one account was missed.
- Leavers keep access to a repository or a shared mailbox nobody thought to check.
- Every request lands as a separate message to a different team.
- When an auditor asks who approved an account, the answer is a chat thread.
The checklist, as a flow
The same steps, in the same order, with the approvals recorded and the exceptions raised rather than quietly skipped.
One form to start it
Role, start date, manager and location decide what gets created. Conditional questions mean nobody fills in fields that do not apply to them.
Approvals where they matter
Pause the flow for a manager or a security owner to approve in Slack or by email, then carry on where it left off with the answer recorded.
Leaving day is a date, not a task
Schedule the offboarding from the leave date, revoke in order, and report anything that could not be removed automatically.
What onboarding looks like in Flomation
From the request to a working account, with the manager asked only once.
- TriggerStarter formRole, date, manager, location
- HumanManager approvalOne click in Slack or email
- ActionCreate accountsDirectory, chat, repositories, licences
- OutputHand overWelcome details out, IT notified
Ready on day one, closed on the last day
Make the checklist run itself
Start with the accounts you create most often, then add the rest as you go. The flow is the documentation, and it cannot be out of date.
Get started