Enhancing the permissions page #6869
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
| </Expandable> | ||
| <Expandable alt_header="Developer"> | ||
|
|
||
| The Developer role is intended for users who build and maintain dbt models under development and manage production behavior. |
There was a problem hiding this comment.
We should add something here about this role being the primary one users will need to develop in the IDE (important to call out especially if the default Member group is removed).
There was a problem hiding this comment.
Added that. Great call out @BrJan !
| </Expandable> | ||
| <Expandable alt_header="Security admin"> | ||
|
|
||
| Security admins have limited access to the security settings and policies for the dbt Cloud account. This is intended for members of a security team who need to ensure compliance with security standards and oversee the implementation of best security practices across the account. |
There was a problem hiding this comment.
This typically should be paired with an IT license (I'll defer to the Enterprise team on specific wording).
There was a problem hiding this comment.
really really like these summaries @matthewshaver i think they're super helpful. good stuff, i have 2 clarifying qs.
|
|
||
| <Expandable alt_header="Account admin"> | ||
|
|
||
| The Account admin role is the highest level of access and control over your dbt Cloud account and projects. We recommend limiting the number of users and groups assigned the account admin role. |
There was a problem hiding this comment.
ooo, love this section. pithy and helpful!
| - The default role assigned to the `Owner` group. | ||
|
|
||
| </Expandable> | ||
| <Expandable alt_header="Admin"> |
There was a problem hiding this comment.
how much is this feedback about the content and how much is about the naming. bc i think it's confusing that there's account admin and admin :( can those be differentiated or is that out of scope?
There was a problem hiding this comment.
I'm listing the permissions as they appear in the product. If we want to get them renamed there (which I agree with) we should give the feedback to the enterprise team through their channels
| </Expandable> | ||
| <Expandable alt_header="Analyst"> | ||
|
|
||
| The Analyst role is designed for users who need to run and analyze dbt models in the IDE but can't create or edit anything outside the IDE. |
website/docs/docs/cloud/manage-access/enterprise-permissions.md
Outdated
Show resolved
Hide resolved
website/docs/docs/cloud/manage-access/enterprise-permissions.md
Outdated
Show resolved
Hide resolved
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
website/docs/docs/cloud/manage-access/enterprise-permissions.md
Outdated
Show resolved
Hide resolved
github-actions
bot
added
size: large
What are you changing in this pull request and why?
Further enhancing the permissions page:
Checklist
🚀 Deployment available! Here are the direct links to the updated files: