Role change
Describe the current role, the proposed change, and why it is needed.
Approval workflow template
Role change approval flow
Use a clear review process before a role or permission change reaches production. This makes it easier to document the reason, the impact, and the sign-off required for each access decision.
Approval checklist
01
Why is the role change needed?
02
What role or hierarchy is changing?
03
Which resources and actions are affected?
04
What relationship or field conditions apply?
05
Who must review or approve the change?
06
What is the rollout and rollback plan?
What to capture in the review
Scope and conditions
Note whether access is limited to an org, a team, a tenant, or a relationship condition.
Risk and approval
List the impacted resources, who signs off, and any rollback or monitoring plan.
When to use it
Use this template when a permission model changes, when a new hierarchy is introduced, or when a role update needs visible approval before engineering closes the work.