From d6b2cdb95e9aa5fa2ce7d2fee03f07dee9cd61b9 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 24 Sep 2024 16:57:08 -0400 Subject: [PATCH] Fixing point --- website/docs/docs/cloud/manage-access/about-access.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/manage-access/about-access.md b/website/docs/docs/cloud/manage-access/about-access.md index c248a4308a1..6b02d9eb17b 100644 --- a/website/docs/docs/cloud/manage-access/about-access.md +++ b/website/docs/docs/cloud/manage-access/about-access.md @@ -115,7 +115,7 @@ There are a few things you need to know before you configure RBAC for SSO users: - New SSO users join any groups with the **Add all new users by default** option enabled. By default, the `Everyone` and `Member` groups have this option enabled. Disable this option across all groups for the best RBAC experience. - You must have the appropriate SSO groups configured in the group details SSO section. If the SSO group name does not match _exactly_, users will not be placed in the group correctly. --dbt Labs recommends that your dbt Cloud group names match the IdP group names. +- dbt Labs recommends that your dbt Cloud group names match the IdP group names. Let's say you have a new employee being onboarded into your organization using [Okta](/docs/cloud/manage-access/set-up-sso-okta) as the IdP and dbt Cloud groups with SSO mappings. In this scenario, users are working on `The Big Project` and a new analyst named `Euclid Ean` is joining the group.