Privilege creep: Update access when roles change

Written by Milutin Jokić | Nov 20, 2026, 2:01:09 PM

Most companies now have a set process for when people join and when they leave. When someone moves within the company, there usually is none. A person who switches from sales to marketing or takes over a team gets new access right away, because otherwise they cannot work. They keep the old access because it bothers nobody.

Over the years, this adds up to a pile of permissions that nobody has an overview of anymore. That is privilege creep. Here is how to update access when roles change instead of letting it accumulate.

Key takeaways

  • Privilege creep happens when employees get new access with every role change but keep the old. The fix is to update access, not just add to it. New access comes right away, old access is removed after a fixed handover period.
  • Accumulated permissions increase the damage of a compromised account, sit badly with the GDPR and cost you licenses.
  • The process starts with a notice from HR. Then you sort every access into one of three groups. It gets added, it stays or it goes.
  • Groups in Google Workspace or Microsoft Entra make role changes easier. Tools with their own login still need a person to remove the access.

Why privilege creep happens

Joining and leaving have a clear trigger. There is a contract, a start date or a resignation, and checklists like our onboarding checklist hang off them. In IT, the three moments are called joiner, mover and leaver. There is plenty of guidance on joiners and leavers, and very little on movers.

The move happens on the side. Often only the team or the job title changes. No new contract is needed, and IT finds out by chance or not at all.

Too much access goes unnoticed. If an account is missing, the employee speaks up on day one. If there is one too many, nobody complains.

Nobody owns the cleanup. The new manager takes care of what is missing. Nobody takes care of what should go, especially since the old team likes to keep the person around for questions for a few more weeks.

What accumulated access costs you

Security. If an account is taken over through phishing, the attacker gets everything the person has collected over the years. That is often far more than the current job requires, which is exactly what the principle of least privilege is meant to prevent.

Separation of duties. Some permissions do not belong together. Someone who moves from accounting to purchasing and keeps their approval rights in online banking can place orders and pay for them too. Germany's IT baseline protection standard from the BSI requires such duties to be kept apart in permissions as well.

Data protection. Under the need-to-know principle, people only see the data their job requires. Article 25(2) of the GDPR requires that personal data is only accessible to the extent the purpose demands. Someone who has left sales no longer needs customer data from the CRM.

License costs. The seat in the old specialist tool stays paid even though nobody uses it. Often this only shows up at renewal.

Audits and customer questionnaires. The BSI module ORP.4 (in German) is clear on this. When staff changes, permissions that are no longer needed must be removed. ISO 27001 expects in Annex A control 5.18 that access rights are provisioned, reviewed, modified and removed. Companies covered by NIS-2 need an access control policy, among other things, under Section 30 of the German BSI Act, and often pass such requirements on to their suppliers. More on this in our guide to BSI requirements.

How to update access when roles change

You do not need an IAM system for this. A fixed trigger, a complete list and clear ownership are enough.

  1. HR reports the move. With the date, old and new role and the new manager, ideally a week ahead.
  2. List the current access. Every tool the person uses, including those with their own login. Add shared passwords, admin roles, folders and channels.
  3. Sort every access. It gets added, it stays or it goes. The previous manager confirms what goes. The new manager decides what gets added.
  4. Set a handover period. Old access only stays active for the handover, two weeks for example. After that, it is removed. Extensions require a reason and a new end date.
  5. Grant new access by role. The basis is a profile that defines which tools belong to a role. This is called role-based access control, and it prevents a collection of one-off requests.
  6. Adjust devices and licenses. Does the new role need a different laptop or other software on the device? Does the plan in a tool change, say from editor to viewer? Reassign or cancel licenses that are no longer needed.
  7. Document it. Record who granted or removed which access and when. That is your proof for the next audit.

Step four is the one that matters most. Without an end date, old access becomes permanent.

Groups instead of individual permissions in Google Workspace and Entra

The more permissions are attached to individual people, the more work every move becomes. If they are attached to groups, the person just switches groups.

In Google Workspace, you can turn services on or off per organizational unit, usually per department, or through access groups. You can also share shared drives and calendars with groups instead of individuals. Switching groups then changes many permissions in one step.

Microsoft Entra works in a similar way. Licenses can be assigned to groups. Microsoft recommends adding the person to the new group first and only then removing them from the old one, so they are not left without a license in between. Dynamic groups can follow the department field, so membership updates automatically when the entry changes. This requires Microsoft Entra ID P1.

Groups only cover tools connected to your central login, though. For tools with their own password, someone still has to remove the access in the tool itself. More on this in our guide to deprovisioning.

Promotion, parental leave, part-time

Promotion. Taking over a team often comes with new permissions for HR data, approvals or tool administration. They belong to the role, not the person, and get the same review at the next move.

Return from parental leave. The BSI recommends temporarily blocking access during longer absences. If someone returns to a different team, the same process applies as for any other move.

Part-time, cover, projects. Fewer hours do not change permissions, unless the tasks change too. Access for covering a colleague or for a project gets an end date from the start.

Check regularly with an access review

Even the best process misses something. That is why a regular access review is part of it. The BSI requires documented permissions to be compared regularly against the actual state and current tasks.

In practice, each tool owner gets the list of users once a quarter or every six months and checks it against current roles. Start with admin roles and the tools that hold customer, financial or HR data. Accounts nobody has used in months are a good sign of leftover access, as our guide to finding unused licenses explains.

Checklist for role changes

  • HR has reported the move with the date, old and new role
  • All current access is listed, including own logins, shared passwords and admin roles
  • Every access is sorted as added, staying or going
  • The handover period is set, with a date and an owner
  • New access is granted by role, groups in Google Workspace or Entra are updated
  • Device, software on the device and licenses fit the new role
  • After the handover period, old access is removed, shared passwords are changed and every step is documented with a date

How Sovaro helps

Sovaro shows which apps each employee actually uses, including tools teams booked themselves. You also see who the tool admin is for each one. When someone changes roles, you give each tool admin their task with a deadline. New access is requested in Slack and approved by the tool admin. Your team removes old access in the tool itself. Sovaro shows what is still open, and the proof for your next audit builds up along the way. Try it for free

Frequently asked questions

What is privilege creep?

Privilege creep is when employees get new permissions with every role change but keep the old ones. After a few years, they have far more access than their job requires.

Who is responsible for access when someone changes roles?

HR reports the move, and the managers decide what goes and what gets added. IT or the owners of the individual tools carry it out.

How long can someone keep their old access?

Only as long as the handover takes, and always with a fixed end date. There is no legal deadline. The BSI does require removing permissions that are no longer needed when staff changes.

How often should access be reviewed?

There is no fixed rule, the BSI just says regularly. Once a quarter makes sense for tools with sensitive data and for admin roles, once a year for everything else.