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

Enhancing the permissions page #6869

Open
wants to merge 1 commit into
base: current
Choose a base branch
from
Open

Enhancing the permissions page #6869

wants to merge 1 commit into from

Conversation

matthewshaver
Copy link
Contributor

@matthewshaver matthewshaver commented Feb 4, 2025

What are you changing in this pull request and why?

Further enhancing the permissions page:

  • Expands the definitions of project and account roles
  • Adds each individual role as an expandable section
  • Defines the role
  • Calls out notable features of the roles

Checklist

  • I have reviewed the Content style guide so my content adheres to these guidelines.
  • The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
  • I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
  • The content in this PR requires a dbt release note, so I added one to the release notes page.

🚀 Deployment available! Here are the direct links to the updated files:

@matthewshaver matthewshaver requested a review from a team as a code owner February 4, 2025 21:25
Copy link

vercel bot commented Feb 4, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
docs-getdbt-com ✅ Ready (Inspect) Visit Preview Feb 4, 2025 9:27pm

@github-actions github-actions bot added content Improvements or additions to content size: medium This change will take up to a week to address Docs team Authored by the Docs team @dbt Labs labels Feb 4, 2025
</Expandable>
<Expandable alt_header="Developer">

The Developer role is intended for users who build and maintain dbt models under development and manage production behavior.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

</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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This typically should be paired with an IT license (I'll defer to the Enterprise team on specific wording).

Copy link
Contributor

@faithebear faithebear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooo, love this section. pithy and helpful!

- The default role assigned to the `Owner` group.

</Expandable>
<Expandable alt_header="Admin">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

</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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

love this section too

- No other access to dbt Cloud features.

</Expandable>
<Expandable alt_header="Stakeholder">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does stakeholder have Explorer access? what about Viewer? can both of those be called out if so? i get asked a lot about what level of access is necessary for explorer

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 Docs team Authored by the Docs team @dbt Labs size: medium This change will take up to a week to address
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants