diff --git a/docs/sso-rbac/sso-providers/oidc/azure-ad.md b/docs/sso-rbac/sso-providers/oidc/azure-ad.md index db98ad0145..bcd18680fe 100644 --- a/docs/sso-rbac/sso-providers/oidc/azure-ad.md +++ b/docs/sso-rbac/sso-providers/oidc/azure-ad.md @@ -270,7 +270,7 @@ Port can query the group membership of users who log in through the AzureAD SSO, In order to import Azure AD groups into Port, Port will require the connection app to approve the `Directory.Read.All` permission. -## SCIM Configuration (beta) + diff --git a/docs/sso-rbac/sso-providers/oidc/okta.md b/docs/sso-rbac/sso-providers/oidc/okta.md index 005bf7eb97..e6435c9b92 100644 --- a/docs/sso-rbac/sso-providers/oidc/okta.md +++ b/docs/sso-rbac/sso-providers/oidc/okta.md @@ -138,7 +138,7 @@ To allow automatic Okta group support in Port, please follow these steps: 3.3 Click `Save`. -## SCIM Configuration (beta) + \ No newline at end of file diff --git a/docs/sso-rbac/sso-providers/saml/azure-ad.md b/docs/sso-rbac/sso-providers/saml/azure-ad.md index 89bd0a9920..025373b41a 100644 --- a/docs/sso-rbac/sso-providers/saml/azure-ad.md +++ b/docs/sso-rbac/sso-providers/saml/azure-ad.md @@ -66,7 +66,7 @@ Alternatively, if you are syncing your groups from an on-prem AD into Entra, con -## SCIM Configuration (beta) + diff --git a/docs/sso-rbac/sso-providers/saml/okta.md b/docs/sso-rbac/sso-providers/saml/okta.md index 77c568438d..8f13b7f8cd 100644 --- a/docs/sso-rbac/sso-providers/saml/okta.md +++ b/docs/sso-rbac/sso-providers/saml/okta.md @@ -82,7 +82,7 @@ To expose your Okta groups to Port via the application, follow these steps: These groups will be ingested into Port as teams, enabling you to manage user permissions and RBAC in your Port account. - ## SCIM Configuration (beta) + \ No newline at end of file