Colour theme
Book a consultation

Making access changes follow staff roles

Define joiner, role-change and departure checks so staff keep only the access their role needs in business applications and administrator accounts.

An illustration of a padlock centred inside layered grey digital circles.

A staff member’s access should change when their work changes. In practice, new access is often added promptly while old access stays in place. Accounts can also survive after an employee or contractor leaves.

An access process connects business decisions with changes in each application. An identity tool can help carry out that process, but it needs accurate instructions and verification.

Separate sign-in from permission

Signing in confirms who someone is. Permissions decide what they can do. A successful MFA check doesn’t mean a person should have access to every customer file.

List the applications and records each role needs. Include administrative actions, exports and sharing outside the organization.

Microsoft’s Entra role guidance recommends limiting administrative privilege. Apply the same question to other tools: what permission is required for this task?

Give access requests a business approver

The manager or record owner should approve the business need. IT then sets up that access and checks it works.

Record the role, scope and expected duration. Temporary cover and contractor work need an end or review date.

Keep passwords and recovery details out of the request and sign-off messages. Hand over credentials through the separate process IT has set up.

Treat a role change as removal and addition

When someone changes teams, compare old permissions with the new role. Remove access that no longer has a business purpose.

Check groups, shared mailboxes, file locations and application-specific roles. A job-title change in the directory may not update every connected service.

Verify a representative task with the staff member and confirm that restricted records are no longer available where intended.

Remove access in every system when someone leaves

Agree who tells IT about departures and when access should end. Include contractors, external collaborators and specialist supplier accounts.

Check active sessions, recovery routes, integrations and shared credentials separately. Disabling one central identity may not remove independently created accounts or revoke every token. The 2021 Colonial Pipeline ransomware attack began with the password for a VPN account that was no longer in use and had no MFA.

Keep the business records your retention schedule requires before deleting accounts. Transfer ownership of essential shared content.

Test automation and exceptions

If provisioning is automated, verify the connector’s coverage and failure alerts. Test a harmless account through creation, role change and removal.

Identify services that still need manual steps and assign those steps to a person. Keep exception access visible for review.

Review the result with owners

Compare current permissions with what each role needs, periodically and after significant changes. Review administrator access and inactive accounts explicitly.

Keep evidence of decisions and completed changes. These records can support a review, but an identity product doesn’t make the business compliant by itself. Use the Microsoft 365 review when access spans tenant configuration, collaboration and device management.


Featured Image Credit