Deploy with Enterprise Admin Console changedthird-party/claude-desktop/admin-console
Nearest release: v2.1.318, published 20 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 4 Nov 2026 18:39 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 4 Nov 2026 19:07 UTC.
Upstream edited
Recorded here
Lines+2added
Lines−0removed
From line
51
where the diff opens
First seen
8 Sep 2026
this site's first read of the page
Recorded edits49to this page, all time
The whole hunk
from line 51, old and new numbered
/
from line 51
5151
5252If your company already has a Claude organization that has verified your email domain, usually a Claude Enterprise organization, name that organization's Primary Owner as the Primary Owner of the new one too. The new organization then appears as an additional organization alongside your existing one and uses the existing organization's single sign-on connection, SCIM directory, and verified domains. Your existing organization is not changed. If no existing organization has verified the email domain of the person you name, the new organization starts with its own sign-in settings.
5353
54You can ask for more than one organization, for example a test organization alongside your production one. To share single sign-on and verified domains across them, [verify the Primary Owner's email domain](https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso) in the first organization before you ask for the next, and name the same Primary Owner. Organizations with separate sign-in settings can't verify the same domain.
55
5456## Connect your identity provider
5557
5658Set up single sign-on before inviting users, as described in [Set up single sign-on](https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso). Users then sign in to Claude Desktop through your identity provider, and you can provision them with SCIM. Single sign-on is recommended rather than required. Without it, invited users sign in with their work email address through the standard Claude sign-in, such as a sign-in link emailed to them.
No line in this hunk matches that.