Better explanation of Managed vs Custom roles? #31793
Open
Conversation
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
I'm looking at ways to reduce the confusion around roles & permissions. I noticed the docs don't explicitly cover the main distinction between managed and custom roles, and would like to fix it.
srosenthal-dd
commented
Sep 23, 2025
| [1]: /account_management/rbac/granular_access | ||
| [2]: /account_management/users/#edit-a-user-s-roles | ||
| [3]: /api/latest/roles/#list-permissions | ||
| [3]: /api/latest/roles/#list-permissions |
There was a problem hiding this comment.
I didn't mean to change this line. Might be the change of a newline at the end of the file?
Preview links (active after the
|
srosenthal-dd
commented
Sep 23, 2025
| - Datadog Read Only Role | ||
|
|
||
| All users with one of these roles can read all data types, except for [individually read-restricted][1] resources. Admin and Standard users have write permissions on assets. Admin users have additional read and write permissions for sensitive assets relating to user management, org management, billing, and usage. | ||
| All users with one of these roles can read data, except for [individually read-restricted][1] resources. Admin and Standard users have write permissions on assets. Admin users have additional read and write permissions for sensitive assets relating to user management, org management, billing, and usage. |
There was a problem hiding this comment.
All users with one of these roles can read all data types
This seemed misleading to me. Read Only Role cannot read Audit Trail, for example. Read Only role grants only read access but does not grant ALL read data accesses.
|
Opened DOCS-12139 to assign a Docs writer and follow up with editorial review. |
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.
What does this PR do? What is the motivation?
I'm looking at ways to reduce the confusion around roles & permissions. I noticed the docs don't explicitly cover the main distinction between managed and custom roles, and would like to fix it.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes