Skip to content

docs: clarify Compliance Hub prerequisites and security role requirements#667

Open
denise-msft wants to merge 1 commit into
mainfrom
fix/clarify-compliance-hub-prerequisites
Open

docs: clarify Compliance Hub prerequisites and security role requirements#667
denise-msft wants to merge 1 commit into
mainfrom
fix/clarify-compliance-hub-prerequisites

Conversation

@denise-msft
Copy link
Copy Markdown
Member

Summary

Fixes #633

This is a documentation gap, not a bug. The issue reports that the Compliance Hub is accessible to users with the CSK - Administrator role, while the docs only mention \System Administrator role in the target environment\ under prerequisites — making it unclear whether System Admin is required for ongoing use.

Root Cause

After reviewing the solution's security role definitions in SECURITY_ROLES.md:

  • CSK - Administrator has full Organization-level access to all compliance tables (Compliance Case, Agent Fact Row Counts, Threshold Config, Action Policy)
  • CSK - Maker has no access to any compliance tables
  • There is no separate Compliance Hub security role — access is governed entirely by the CSK roles

The behavior reported in #633 (CSK - Administrator can access the Compliance Hub) is correct and expected. The System Administrator role is only required for initial installation and setup of the solution, not for day-to-day Compliance Hub operations.

Changes

  • Split the prerequisites permissions section into setup vs ongoing use to clarify when System Admin is needed vs when CSK - Administrator suffices
  • Added a cross-reference to SECURITY_ROLES.md for full role details
  • Clarified in the Administrator persona section that CSK - Administrator grants org-level compliance table access
  • Clarified in the Maker persona section that CSK - Maker does not have compliance table access

…ents

Resolves confusion about whether System Administrator role is required
for ongoing Compliance Hub access (#633). The System Administrator role
is only needed for initial setup/installation. Day-to-day Compliance Hub
access is controlled by the CSK - Administrator security role, which
grants full Organization-level access to all compliance tables.

Changes:
- Split permissions into setup vs ongoing use sections
- Add reference to CSK - Administrator role and SECURITY_ROLES.md
- Clarify Administrator persona has org-level compliance table access
- Clarify Maker persona has no compliance table access

Fixes #633

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Compliance Hub visible to CSK - Administrator role

1 participant