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

Snowflake permission note #6573

Open
wants to merge 3 commits into
base: current
Choose a base branch
from
Open

Conversation

matthewshaver
Copy link
Contributor

@matthewshaver matthewshaver commented Dec 2, 2024

What are you changing in this pull request and why?

See internal chat for context: https://dbt-labs.slack.com/archives/C02NCQ9483C/p1732724200239919?thread_ts=1732650446.311849&cid=C02NCQ9483C

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 December 2, 2024 21:13
Copy link

vercel bot commented Dec 2, 2024

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

Name Status Preview Updated (UTC)
docs-getdbt-com ✅ Ready (Inspect) Visit Preview Dec 3, 2024 0:47am

@github-actions github-actions bot added content Improvements or additions to content size: small This change will take 1 to 2 days to address Docs team Authored by the Docs team @dbt Labs labels Dec 2, 2024
@@ -5,6 +5,14 @@ description: "Configure Snowflake connection."
sidebar_label: "Connect Snowflake"
---

:::note

A crucial part of working with dbt atop Snowflake is ensuring that users in development environments and/or service accounts in deployment to production environments have the correct permissions to take actions on Snowflake.
Copy link
Contributor

Choose a reason for hiding this comment

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

i'm not sure if we need this intro here

Suggested change
A crucial part of working with dbt atop Snowflake is ensuring that users in development environments and/or service accounts in deployment to production environments have the correct permissions to take actions on Snowflake.
dbt Cloud works with Snowflake by inheriting permissions directly from your Snowflake data platform configuration. This ensures you have full control over what dbt Cloud can access. You can customize roles and permissions in Snowflake to fit your company's requirements and manage access to database objects.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's the original not deleted below. I'm ok with removing it, but we should be careful with this language. We don't want to inadvertently indicate that Snowflake user permissions can somehow be assigned to users in dbt Cloud itself (for their permissions over the dbt account). How about:

Suggested change
A crucial part of working with dbt atop Snowflake is ensuring that users in development environments and/or service accounts in deployment to production environments have the correct permissions to take actions on Snowflake.
dbt Cloud connections and credentials inherit the permissions of the accounts configured. You can customize roles and associated permissions in Snowflake to fit your company's requirements and fine-tune access to database objects in your account. See [Snowflake permissions](/reference/database-permissions/snowflake-permissions) for more information about customizing roles in Snowflake.


A crucial part of working with dbt atop Snowflake is ensuring that users in development environments and/or service accounts in deployment to production environments have the correct permissions to take actions on Snowflake.

You can customize roles and associated permissions in Snowflake to fit your company's requirements and fine-tune access to database objects in your account. See [Snowflake permissions](/reference/database-permissions/snowflake-permissions) for more information about customizing roles in Snowflake.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
You can customize roles and associated permissions in Snowflake to fit your company's requirements and fine-tune access to database objects in your account. See [Snowflake permissions](/reference/database-permissions/snowflake-permissions) for more information about customizing roles in Snowflake.
Refer to [Snowflake permissions](/reference/database-permissions/snowflake-permissions) for more information about customizing roles in Snowflake.

Copy link
Contributor

@mirnawong1 mirnawong1 left a comment

Choose a reason for hiding this comment

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

hey @matthewshaver , left some suggestions here!

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: small This change will take 1 to 2 days to address
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants