Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify levels in RBAC permissions table #5742

Closed
1 task done
mirnawong1 opened this issue Jul 5, 2024 · 0 comments · Fixed by #5751
Closed
1 task done

Clarify levels in RBAC permissions table #5742

mirnawong1 opened this issue Jul 5, 2024 · 0 comments · Fixed by #5751
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear

Comments

@mirnawong1
Copy link
Contributor

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

@b-per shared some feedback about how the RBAC docs aren't easy to understand. He shared the attached screenshot asking for more information about what those permissions really mean for dbt Cloud users.

image

For example, what does the R/W access to “dbt adapters” mean? And does “Credentials” refer to Env credentials or Dev credentials or both?

Raised this in internal slack for confirmation

What part(s) of the page would you like to see updated?

https://docs.getdbt.com/docs/cloud/manage-access/enterprise-permissions

Additional information

No response

@mirnawong1 mirnawong1 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels Jul 5, 2024
@mirnawong1 mirnawong1 changed the title Clarify levels in RBAC permissions table Clarify levels in RBAC permissions table and improve table based on user feedback Jul 8, 2024
@mirnawong1 mirnawong1 changed the title Clarify levels in RBAC permissions table and improve table based on user feedback Clarify levels in RBAC permissions table Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant