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.

Sign up for GitHub

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

Jump to bottom

Clarify metadata permissions on enterprise permissions page #5059

Closed
1 task done
mirnawong1 opened this issue Mar 11, 2024 · 1 comment
Closed
1 task done

Clarify metadata permissions on enterprise permissions page #5059

mirnawong1 opened this issue Mar 11, 2024 · 1 comment
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

Support raised that we should clarify that the Metadata permission set is only for Service tokens for the Discovery API. This was due to a ticket where a customer attempted to add the Metadata permission set in a Group.

Wondering if we should include an asterisk disclaimer specifying it applies to disco api.

Slack thread

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 Mar 11, 2024
@matthewshaver
Copy link
Contributor

Fixed in #5066

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matthewshaver @mirnawong1