One read of Claude Documentationclaude-docs-20260827T213714Z
2 pages moved out of 218 read.
Pages moved
2
significant first
Pages read
218
in this capture
Captured
21:37 UTC
Corpus hash
ac7ae7a20dc3
corpus-hash
What this read moved
1-2 of 2government/tenant-admin/identity-and-access Changed · +2 / -0 lines
from line 45
4545
4646After you save a SAML connection, an **SP metadata URL** appears alongside these values. Most identity providers can import this address to fill in the other values automatically if you need to reconfigure.
4747
48People start sign-in from Claude Desktop (**Sign in with your organization**) or from the web portal in a browser, and Claude for Government then sends them to your identity provider. Starting from the application's tile in your provider's app portal (such as Microsoft My Apps), or from a sign-in test in your provider's admin console, is not supported.
49
4850### Connecting with OIDC
4951
5052If your identity provider supports OpenID Connect, fill in the OIDC section:
government/tenant-admin/setup-wizard Changed · +2 / -0 lines
from line 38
3838
3939Until single sign-on is connected, only owners who were invited directly by email can sign in. The full field reference for both protocols is on the [Identity and access](/docs/government/tenant-admin/identity-and-access#single-sign-on) page.
4040
41Once single sign-on is connected, people sign in from Claude Desktop or the web portal, and Claude for Government sends them to your provider from there. Starting from the application's tile in your provider's app portal, or from a sign-in test in its admin console, is not supported.
42
4143## Step 4: Provisioning (optional)
4244
4345This step is optional. If your identity provider supports SCIM, which is a standard way for directory systems to push users and group memberships into other applications, you can connect it here so that accounts are created automatically rather than at first sign-in.