Review SaaS accounts
Collect user lists from each SaaS admin console and match them to current employees. Leavers' and long-unused accounts are disabled only after approval.
The problem today
Every quarter, IT exports users from more than a dozen SaaS consoles and matches them with the employee list. Name differences make matching slow, and leavers' accounts can be missed.
The workflow in Kitewell
- Get the current employee list from the HR systemAutomatic
- Collect users and last sign-in dates from each SaaS consoleWeb
- AI identifies accounts of leavers and long-unused accountsAI judgment
- IT approves which accounts to disableApproval
- Disable approved accounts and record the resultWeb
What AI does
Matches users against employees despite differences in name spelling and email address, and suggests accounts of leavers and long-unused accounts.
Where people decide
Accounts are disabled only after approval. Sending the list back makes the workflow revise it and ask for approval again.
Features used
What a PoC checks
- Whether user lists can be collected from each SaaS console
- Whether the matching rules fit your internal process
- Which accounts to disable automatically and which to leave to people
Discuss a PoC for this work
We check whether this workflow runs on your own work and screens.
Related use cases
Enter an Excel list into a web system
For each row of an Excel list of orders, AI enters it into a web system and writes the receipt number back into the row. Only failed rows are redone.
Check property listings across portals
Your Excel property register is compared with each listing portal, and any difference in rent or availability goes into the row and to the person responsible.
Reconcile rent payments
Match internet banking deposits against the tenant register. When the payer name differs from the tenant's, AI suggests the matching lease.