Dbt cloud docs/update enterprise permissions #1805
Closed
Conversation
This file contains 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
Initial docs for dbt v0.20.0
…standard-args Clarify standard args for generic tests
Rewrite dispatch docs
…ilures-new-configs Tests: store failures, new configs
Changes ahead of 0.20.0rc1 announcement
fix typo - should be `dbt test`
* Edits for on_schema_change * dbt source freshness * DBT_ENV_SECRET_ env var * dbt build first cut * Redshift profile ra3 property * Beta callout in migration guide * Self-review build docs
* state:modified subselectors, modified.macros * Add build RPC method * PR feedback
* Switch --models to --select * BQ snapshot config aliases * Configurable postgres connect timeout * Add list --output-keys. Add list RPC method * Adapter unique_field dbt-labs/dbt-core#3796 * PR feedback: -s replaces -m * Add BQ execution_project * Add default property for yaml selectors * Update migration guide. New fields in sources.json * Test where config macro * Dispatch for global macros * Update build details * Some self review * Greedy flag/property for test selection * Resolve #803 while we're here * Fix broken link typo
* Very incomplete start of first draft * Second big pass * Initial self review. Sidebar reorg * Continue self review. Address #616 * Add note to migration guide
✅ Deploy Preview for docs-getdbt-com ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
github-actions
bot
added
content
|
Hey @matt-winkler let me know when this is ready fro review and either @nghi-ly or I will review it! |
|
Thanks @runleonarun - are you conceptually on board with updating our documentation along the lines of the example I gave for Job Admin here? Anyone else we'd need to loop in on that decision? I'm asking a few more questions up front because doing this would illustrate more detail than we've shown historically on this page, so I want to be mindful of the suggested change in approach. |
mirnawong1
added
the
merge-conflict-cli
|
Closing due to age - we have since redesigned the permissions page to more accurately display what each role has access to https://docs.getdbt.com/docs/cloud/manage-access/enterprise-permissions |
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.
Description & motivation
The goal of this PR is to document more specifically which
actionsusers can take based on their assigned permission sets.dbt Cloud users sometimes encounter challenges with understanding the actions users can take based on their assigned permission sets. In some cases, the current documentation on this page omits key capabilities. For example with the
Job Adminpermission set, the docs don't state the ability to create dbt Cloud jobs, although a user can in fact create new jobs with this permission set.To-do before merge
Align on approach to communicating this information.
Prerelease docs
If this change is related to functionality in a prerelease version of dbt (delete if not applicable):