From f5731de001fd0daced6074c899da50347dd83752 Mon Sep 17 00:00:00 2001
From: ably-sync-bot <65761964+ably-sync-bot@users.noreply.github.com>
Date: Tue, 14 Apr 2026 17:59:48 +0100
Subject: [PATCH] Update callout to explicitly reference first_name and
 last_name attributes

Eliminate duplicate SSO provisioning note

Removed duplicate note about just-in-time provisioning for SSO from Okta and Google Workspace sections.
---
 src/pages/docs/platform/account/sso.mdx | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/pages/docs/platform/account/sso.mdx b/src/pages/docs/platform/account/sso.mdx
index 31388d71db..e9d969d7ec 100644
--- a/src/pages/docs/platform/account/sso.mdx
+++ b/src/pages/docs/platform/account/sso.mdx
@@ -16,6 +16,10 @@ Any SAML-compatible identity provider can be used to enable SSO.
 
 The following instructions are examples of configuring SSO with [Okta](#okta) and [Google Workspace](#google).
 
+<Aside data-type='note'>
+When a user signs in via SSO for the first time, Ably uses just-in-time (JIT) provisioning to automatically create their account. The `first_name` and `last_name` attributes are used to set the user's display name. If they are missing or empty, provisioning will fail and the user won't be able to sign in. This does not apply if you are using SCIM to provision users.
+</Aside>
+
 ### Okta <a id="okta"/>
 
 To enable SSO using [Okta](https://www.okta.com/) as the identity provider, configure the following properties in your Ably account dashboard and your Okta account: