update sl credentials flow #6008
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
There was a problem hiding this comment.
As a high level note - there are no pictures of a functioning Teams or Enterprise SL Details page. That's what the user should see when they are doing a number of actions:
- link new service token
- unlink a service token
- delete credentials
And while I'm not sure we need a screen capture for EVERY one of those, having at least one image where people would see the correct "edit" button and the link/unlink options and the delete credential option seems like it would be useful.
|
(I didn't approve or request changes because I'm not sure I'm the person whose review you wanted :P ) |
…t.com into update-SL-credential
|
that's amazing, thanks so much for your feedback @theyostalservice ! I've taken them all onboard and folded them in - really appreciate it! |
| 1. In the **Set Up Semantic Layer Configuration** page, enter the credentials specific to your data platform that you want the Semantic Layer to use. | ||
| 1. After selecting the deployment environment, you should see the **Credentials & service tokens** page. | ||
| 2. Click the **Add Semantic Layer credential** button. | ||
| 3. In the **1. Add credentials** section, enter the credentials specific to your data platform that you want the Semantic Layer to use. |
There was a problem hiding this comment.
| 3. In the **1. Add credentials** section, enter the credentials specific to your data platform that you want the Semantic Layer to use. | |
| 3. In the **Add credentials** section, enter the credentials specific to your data platform that you want the Semantic Layer to use. |
There was a problem hiding this comment.
Hiya @mirnawong1
I haven't committed this as I was't sure if the addition of the number 1 was intentional. This is a non-blocker btw.
Kind Regards
There was a problem hiding this comment.
yes it's intentional bc it's par of the cloud ui flow and I'm referring to it. great question!
| 2. Name the token and save it. Once the token is generated, you won't be able to view this token again so make sure to record it somewhere safe. | ||
| <Lightbox src="/img/docs/dbt-cloud/semantic-layer/sl-add-credential.jpg" width="55%" title="Add credentials and map them to a service token. " /> | ||
|
|
||
| 4. After adding credentials, scroll to **2. Map new service token**. |
| 2. On the **Create New Semantic Layer Credential** page, you can create multiple credentials and map them to a service token. | ||
| 3. In the **Add credentials** section, fill in the data platform's credential fields. We recommend using “read-only” credentials. | ||
| 1. After configuring your environment, on the **Credentials & service tokens** page, click the **Add Semantic Layer credential** button to create multiple credentials and map them to a service token. | ||
| 2. In the **1. Add credentials** section, fill in the data platform's credential fields. We recommend using “read-only” credentials. |
|
|
||
| 5. Click **Save** to link the service token to the credential. Remember to copy and save the service token securely, as it won't be viewable again after generation. | ||
| <Lightbox src="/img/docs/dbt-cloud/semantic-layer/sl-credential-created.jpg" width="100%" title="Manage multiple credentials and link them to service tokens for more granular control."/> | ||
| 3. In the **2. Map new service token** section, map a service token to the credential you configured in the previous step. dbt Cloud automatically selects the service token permission set you need (Semantic Layer Only and Metadata Only). |
Co-authored-by: nataliefiann <[email protected]>
There was a problem hiding this comment.
Hiya @mirnawong1
This is a great PR! Thank for posting this! I've approved this for you - I left some non-blocking suggestions and questions but nothing to drastically change the doc / PR.
Kind Regards
this pr updates the SL credentials setup section, screenshots, and adds a table to try to better explain service tokens and credentials, and how they relate to diff plans.
[ ] needs PM review