From e92b70dbbf8ecee0ddbbbeae196603918d1b5f6d Mon Sep 17 00:00:00 2001 From: Sarah Sanders Date: Mon, 28 Oct 2024 09:21:27 -0700 Subject: [PATCH] Update content/manuals/security/for-admins/provisioning/group-mapping.md Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com> --- .../manuals/security/for-admins/provisioning/group-mapping.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/manuals/security/for-admins/provisioning/group-mapping.md b/content/manuals/security/for-admins/provisioning/group-mapping.md index 8a5002dd07..93b8e425dc 100644 --- a/content/manuals/security/for-admins/provisioning/group-mapping.md +++ b/content/manuals/security/for-admins/provisioning/group-mapping.md @@ -28,7 +28,7 @@ To assign users to Docker teams through your IdP, you must create groups in your You can also use this format to assign users to multiple organizations. For example, to add a user to the "backend" team in the "moby" organization and the "desktop" team in the "whale" organization, the group names would be `moby:backend` and `whale:desktop`. ->[!TIP] +> [!TIP] > >Match the group names in your IdP with your Docker teams. When groups are synced, Docker creates a team if it doesn’t already exist.