Background
The RBAC management user manual is being updated in PR #7446 (docs(rbac): align with revoke/remove confirmation flow and localized scope names). The new copy documents:
Delete a Permission → Remove a Permission (popconfirm UX)
Remove Users from a Role → Revoke Users from a Role (popconfirm UX)
- The convention: "this action is treated as reversible and uses a lightweight popup confirmation rather than a typed-name confirmation modal"
This convention is exactly the one codified in .claude/rules/destructive-confirmation.md (FR-2479) and currently being rolled out across the project by FR-2819 (typed modal for irreversible deletes) and FR-2825 (Popconfirm for reversible activate/deactivate / revoke).
Scope
Verify and, if needed, supplement the docs so that the RBAC manual matches what FR-2819 / FR-2825 actually ship:
Out of scope
- Re-litigating the confirmation UX rule itself — that is settled (FR-2479).
- Code changes to the RBAC pages — those belong to FR-2819 / FR-2825.
References
JIRA Issue: FR-2909
Background
The RBAC management user manual is being updated in PR #7446 (
docs(rbac): align with revoke/remove confirmation flow and localized scope names). The new copy documents:Delete a Permission→Remove a Permission(popconfirm UX)Remove Users from a Role→Revoke Users from a Role(popconfirm UX)This convention is exactly the one codified in
.claude/rules/destructive-confirmation.md(FR-2479) and currently being rolled out across the project by FR-2819 (typed modal for irreversible deletes) and FR-2825 (Popconfirm for reversible activate/deactivate / revoke).Scope
Verify and, if needed, supplement the docs so that the RBAC manual matches what FR-2819 / FR-2825 actually ship:
rbac_revoke_popconfirm.png,rbac_permission_modal.png) match the current popconfirm + modal copy after FR-2825 lands.Out of scope
References
JIRA Issue: FR-2909