Reset permissions when an employee changes teams
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A sales employee moves into service. The new manager requests access to the service queue, and an administrator adds it. Nobody removes opportunity exports, discount approvals, or campaign permissions. The employee can now do both jobs, even though only one is theirs.
An employee role change access review should replace the old permission set with one justified by the new duties. Compare the two roles, identify permissions that must end, approve any necessary overlap with an expiry date, and test the resulting access. Do not close the request simply because the new tools work.
The worksheet below makes that process concrete. It records what the employee needs to do, where access comes from, who authorises each decision, and what evidence will show that the change worked. It covers permanent internal moves, not departures, training plans, or reassignment of customer ownership.
1. Start with the difference between the jobs
A job title is too broad to decide access. Ask the outgoing and incoming managers to describe the actual actions the employee will stop and start performing. Then translate those actions into permissions.
For each duty, separate viewing information from changing it, approving it, exporting it, or sending it externally. An employee may need to read an account's service history without needing a bulk download of the account database. They may need to answer assigned conversations without needing to configure a shared inbox.
Use three questions to expose the difference:
- What ends? Which previous responsibilities stop on the move date, and which permissions existed only to support them?
- What begins? Which new responsibilities require access, and what is the narrowest useful scope?
- What continues? Which duties genuinely remain, rather than merely being familiar or convenient?
Classify access as retained, removed, added, or temporarily overlapping. Retained access needs a current business reason; having it already is not a reason. Overlap needs a specific unfinished task, not a general request to keep everything for a while.
This approach is consistent with OWASP's least-privilege guidance: permissions should be limited to what the work requires. That guidance is a design principle, not evidence that a particular workspace enforces it.
2. Inventory effective access, not just the visible role
Before making changes, record the employee's current access and how each permission is granted. A role label alone can miss a direct grant, a second group, or access in a separate communications workspace.
Review the applicable access routes:
- Team memberships, role bundles, and permissions assigned directly to the employee.
- Record-level or queue-level sharing that grants access beyond the main role.
- Separate workspaces, shared inboxes, reporting tools, and connected applications used for the old duties.
- Approval authority, exports, bulk actions, configuration rights, and permission-management rights.
- Active sessions or employee-linked credentials that require attention when permissions change.
Record only routes that actually exist in your environment. Do not assume that removing one group removes a permission everywhere. Equally, do not remove a broad group without checking whether it also supplies access required for the new role.
Assign responsibility before execution. The outgoing manager confirms which duties end. The incoming manager confirms what the new role requires. The relevant system or data owner authorises sensitive access and exceptions. An administrator implements the approved change, and a named reviewer checks the outcome. In a small business, one person may fill several of these roles, but the decisions should still be recorded separately.
3. Filled hypothetical mover worksheet: sales to service
Fictional worked example: The employee, dates, systems, and permission arrangements below are hypothetical. They illustrate a recommended process, not existing product controls or customer results.
Move details and duty comparison
- Employee: Maya Chen.
- Permanent move: Sales executive to service coordinator, effective 14 September 2026.
- Outgoing manager: Daniel Ortiz. Incoming manager: Priya Shah.
- Implementer: Workspace administrator Alex Morgan. Verification owner: Operations lead Jordan Lee.
- Duties ending: Editing sales opportunities, exporting prospect lists, approving sales discounts, and preparing outbound campaigns.
- Duties starting: Reviewing assigned service cases, updating service records, and responding through the service team's assigned conversation queue.
- Duties continuing: Maintaining Maya's own profile and reading account details needed for assigned work.
- Limited transition task: Answering internal questions about two identified opportunity records until 17 September. No sales edits, approvals, exports, or customer outreach are required for that task.
Retained permissions
- Own profile and personal preferences: Retain through the basic employee role. Reason: required in either job. Approver: Priya. Review: 14 September, then during the next role review. Check: Maya can update her own preferences but cannot administer another employee's account.
- Read account details for assigned work: Retain the function, but replace the sales-team scope with the service-assignment scope on 14 September. Grant route: service role, after removing the sales role. Approver: Priya and the account-data owner. Review: 14 September. Check: an assigned service account is visible; an unrelated sales account is not.
Removed permissions
- Opportunity creation and editing: Remove the sales role and any direct edit grants on 14 September. Approver: Daniel. Review: 14 September. Check: Maya cannot create an opportunity or save a change to an existing one.
- Prospect-list export: Remove the direct export grant on 14 September. Approver: sales-data owner. Review: 14 September. Check: an authorised export attempt is denied, including any separately available reporting route.
- Sales discount approval: Remove approval-group membership on 14 September. Approver: Daniel. Review: 14 September. Check: Maya cannot approve a test request; the sales manager separately confirms that no outstanding approval still depends on her.
- Campaign preparation and launch: Remove the campaign-editor role in the communications workspace on 14 September. Approver: communications owner. Review: 14 September. Check: Maya cannot create or launch a campaign. Her new service queue access is checked separately.
Temporary overlapping permission
- Read-only access to two named opportunity records: Grant a narrowly scoped exception, if supported, from 14 through 17 September. Purpose: answer internal questions about the recorded history. Approvers: Daniel and the sales-data owner.
- Excluded actions: No editing, exporting, approval authority, or wider sales-team visibility.
- Review date: 16 September. Daniel confirms whether the questions are resolved; remove access early if they are.
- End date: 17 September, with removal owned by Alex and verification owned by Jordan. If automatic expiry is unavailable, use a scheduled removal task and a separate verification task.
- Alternative if narrow access is unavailable: Do not retain the broad sales role. Daniel retrieves the necessary record context and answers the internal question with Maya.
Added permissions and completion evidence
- Assigned service cases: Add read and update access through the service role on 14 September. Approver: Priya. Review: 14 September. Check: Maya can update an assigned test case but cannot change an unrelated restricted case.
- Assigned service conversations: Add the service queue role on 14 September. Approver: communications owner. Review: 14 September. Check: Maya can handle a controlled test conversation, without receiving campaign or workspace-administration permissions.
- Move-day evidence: Retain the approved worksheet, before-and-after permission records, test outcomes, and any unresolved exception in the access-change record.
- Closure condition: Keep the review open until the temporary opportunity access has been removed and its removal verified on 17 September.
4. Make overlap an exception with an exit
Temporary overlap can be reasonable when an unfinished task requires information from the old role. It becomes permission accumulation when nobody names the task, limits the scope, or owns the end date.
Ask whether the work can be completed before the move, handled by the outgoing manager, or supported with narrower read-only access. These alternatives may add coordination, but they avoid keeping an entire previous role active for a small dependency.
When overlap is necessary, record its purpose, exact scope, approver, review date, removal date, and removal owner. The review date creates a chance to end access early. The removal date establishes when the exception must stop unless a fresh decision is authorised.
If the task is unfinished at expiry, do not silently extend the permission. Reassess what remains and whether the same scope is still needed. A series of extensions may mean the employee's duties have not actually changed as described. Resolve that mismatch with the managers rather than disguising an ongoing responsibility as temporary access.
5. Execute the move as a replacement
Translate the worksheet into an ordered change plan. The objective is to avoid both an uncontrolled dual-role period and a service interruption caused by removing access before its replacement is ready.
- Capture the starting state. Record relevant roles, groups, direct grants, and scoped exceptions so discrepancies can be investigated.
- Confirm approvals and timing. Agree when the old duties end and who is available if a critical new-role task fails.
- Prepare the new scope. Check that the intended role exists and provides the necessary access without unrelated authority.
- Apply the approved replacement. Remove obsolete grant routes, add new-role access, and establish only the approved temporary exceptions.
- Verify immediately. Test required work and prohibited actions before treating the move-day change as complete.
- Track remaining exceptions. Keep the overall review open until their removal is checked.
Exact ordering depends on the system and operational needs. Where changes cannot be applied together, keep any transition interval controlled and explicitly approved. Check how permission changes affect active sessions; do not assume an open session immediately reflects the new state.
6. Test what should work and what must fail
A successful login proves little. Verification needs positive tests for the new duties and negative tests for the permissions that should have ended.
Use authorised test records and controlled actions. Avoid exporting live information merely to prove that export is blocked, or sending a real customer message solely to test queue permissions. Do not ask the employee to share credentials; use an approved verification method.
- Positive test: Can the employee open and update the assigned service case?
- Scope test: Is an unrelated restricted record inaccessible?
- Removal test: Is an old sales edit or export denied?
- Exception test: Can the employee read only the specifically approved transition records?
- Expiry test: After removal, are those transition records no longer accessible?
Where applicable, check access through saved links as well as menus. A missing menu item is not proof that the underlying record is protected. OWASP's object-level authorization guidance explains that access must be authorised for the requested object; knowing its identifier does not grant permission.
Record the expected result, observed result, date, and tester. A settings screenshot can support the record, but it does not substitute for checking effective access.
7. Recover without restoring the whole old role
If a legitimate service task fails, identify the missing action and scope before restoring access. Reinstating the entire sales role may fix the immediate problem while undoing the review. Prefer a targeted, authorised correction, then repeat the relevant positive and negative tests.
If an old permission still works, trace every grant route. The cause may be another group, a direct exception, separate workspace access, or session behaviour. Record the unexpected result, remove the unintended route, and retest rather than repeatedly editing the same visible role.
If narrow permissions are unavailable, document the limitation and choose an alternative workflow with the responsible owner. A manager-mediated lookup may be workable; broad access should not become the default merely because it is easier to configure.
If temporary access expires before removal is verified, treat the review as incomplete. Escalate to the named owner and check actual access. A completed reminder is not evidence that the permission ended.
8. Make the next move measurable
For the next permanent transfer, complete the worksheet before the effective date. List every identified old-role permission, give it a disposition, name its approver, and specify a verification result. Any temporary overlap must also have an owner and an end date.
Track three counts for that move: permissions awaiting a decision, failed verification checks, and overdue temporary exceptions. The intended closure condition is zero in each category—not because a ticket says complete, but because the resulting access has been checked.
Schedule the first review of those counts when the move is approved. That gives the administrator a concrete finish line: the employee can perform the new duties, cannot exercise obsolete authority, and has no unreviewed access left over from the previous team.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications