Update from code changes: developers can verify content#933
Open
mintlify[bot] wants to merge 1 commit into
Open
Update from code changes: developers can verify content#933mintlify[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.
|
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
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
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
Reflect that manual chart and dashboard verification is now a developer capability, and document the explicit save-time warning shown to users who can't preserve verification.
Changes
references/workspace/roles.mdx: added a Verify and unverify charts and dashboards row to the Project Roles matrix (Admin and Developer only).guides/verified-content.mdx: updated Who can verify content to include developers (plus custom roles withmanage:ContentVerification), reworded the CLI permissions section accordingly, and added a What you see when saving verified content section covering the two dialog variants (keep-or-drop for verifiers, warning with Cancel / Save anyway for everyone else).Context
manage:ContentVerificationto the developer role.