docs: clarify role requirements for compliance actions#285
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: clarify role requirements for compliance actions#285mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
GKestenberg
approved these changes
May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document that enabling compliance controls and re-running infrastructure provisioning from the compliance dashboard require an admin or developer project role, while viewers retain read-only access.
Changes
Context
Triggered by an upstream change that hides mutation affordances (the Enable controls button, the cost-consent action, and the Re-run infrastructure provisioning links) for users with the viewer role and replaces them with an explanatory message. The docs previously did not mention any role requirement for these actions.