Lesson 5 of 10 · About 5 minutes

Handling role changes

Learn the concept.

A transfer is both an addition and a removal decision. Giving a person the new role without reviewing the old one creates access accumulation.

Compare old and new needs

Identify access to retain, add, and remove. Include direct grants and group-based access.

Coordinate the transition

Confirm the effective date and any approved overlap. Record temporary access with an expiry.

Verify the result

Check effective access in relevant applications rather than assuming a group change reached every system.

Field example05 / A

Put it in context

Maya moves from finance to support. She needs ticket access; payment approval should be removed unless an authorized, time-limited exception exists.

SEE THE IDEA

A transfer has three decisions

Maya moves from finance to support.

A transfer has three decisions
Existing or new accessDecisionReason
Payment approvalRemoveNo longer justified unless a specific approved exception applies
Shared employee resourcesRetainStill needed in the new role
Support ticket accessAddNew approved job requirement
Confirm timing, direct grants, group membership, and any time-limited overlap. Verify effective access in the applications.
Read the visualWhat goes wrong if you only add the support group?

Old permissions may remain and accumulate across transfers.

Make a decision.

Use what you just learned. A correct answer lets you save this lesson to your progress.

Take this with you.

A mover needs an access comparison, not just more permissions.

YOUR LEARNING SPACE