Clarify how user can replace API key with PAT #4914
Labels
content
Improvements or additions to content
improvement
Use this when an area of the docs needs improvement as it's currently unclear
Contributions
Link to the page on docs.getdbt.com requiring updates
Per user feedback in slack, the existing user token page should clarify or go into detail how a user should replace the api key. Currently, some users think they have to replace their API key in dbt Cloud with their new PAT.
Instead, they should use the PAT anywhere they previously used an API key:
Also the the 'user api tokens' in the callout doesn't direct the user anywhere and needs updating to
#user-api-tokens
What part(s) of the page would you like to see updated?
https://docs.getdbt.com/docs/dbt-cloud-apis/user-tokens#account-scoped-personal-access-tokens
Additional information
No response
The text was updated successfully, but these errors were encountered: