Profile
Creating accounts usually happens on time. Removing them does not, because nobody notices, until an audit or an incident.
The Access Manager links staff changes to accounts and permissions, and keeps track of what stays open.
What it may do itself and what goes past a person is set per system. With access, the default is cautious.
What it does, step by step
- Receive the changeA new starter, a change of role or a leaver, from HR.
- Determine the access profileWhich systems and which role belong to this job, according to your own matrix.
- Prepare the requestPer system, with the approval it needs.
- Carry out or referStandard access can be automatic; sensitive systems always go past a person.
- Flag lingering accessAccounts of people who have left, permissions that stayed after a change of role.
Works with these systems
- Microsoft 365
Azure DevOps- APIs
- AFAS
- Databases
Jira Service Management- Freshdesk
Is your system not listed? We can connect any system, even if there is no standard integration. View all integrations.
What runs automatically and what does not
You stay in control.
Not every decision should be made automatically. For each workflow, we set out:
- What can happen automatically.
- What is put forward for approval first.
- When a person is brought in.
- What information is stored.
- How actions are logged.
Is this a fit for your organisation?
A good fit if
- Organisations with regular joiners and leavers.
- Businesses with an ISO or NIS2 obligation on access management.
- Situations where permissions linger after a change of role.
Less of a fit if
- Very small organisations where one administrator sees everything.
- Organisations without a role matrix: build that first, or you automate the mess.
What it can deliver
- New hires who can work on day one.
- Fewer accounts left open after someone leaves.
- Demonstrable access management for an audit.
Directions, not promises. As soon as there is evidence from a client project, it will appear here as a substantiated result.
Frequently asked questions
Can an AI employee create accounts and grant permissions itself?
For standard access that comes with a job, yes, as long as it follows your role matrix. For sensitive systems, admin rights and anything involving financial or personal data, we add human approval by default.
Does this help with ISO 27001 or NIS2?
It helps you demonstrate access management, which is one of the hardest points in both frameworks. It produces a log of who got which access, when and on what grounds. Certification is of course broader than this.
How does it know someone is leaving?
From your HR system. If leavers are handled by email or in a conversation, that is the first thing we set up together, because without a reliable source this stays manual work.
What happens to the accounts of people who have left?
They are flagged and handled according to your procedure: block, archive or hand over. Exactly what happens and who confirms it, we record, because deleting a leaver's data cannot be undone.
How to put this to work
- 1A short callTogether we look at your process and your systems, and whether this task is the best place to start.
- 2Set up on your rulesIntegrations with your own systems, and agreeing what may run automatically and what a person approves.
- 3Measure and adjustFirst alongside your team, only then on its own. We look at what it delivers and adjust.