You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- One entitlement gate: the deployment flag is the outer gate everywhere
(authentication, admin API, reconcile job, discovery)
- Group PATCH: path-less add contributes members; add without a value is
refused; filter booleans only for active; formatted name applied after
its parts
- Projection: mappings to workspaces that left the organization are
ignored and their provenance dropped without touching the other tenant
- Update refuses a stale row for someone who left; deprovision serializes
on the user locks and scopes account-wide effects to a real removal
- Auto-map drops the stale automatic mapping on rename; mapping upserts
are conflict-safe and refuse the default group; connection settings
merge under the row lock
- Relinking keeps email verification when the address is unchanged;
addresses are syntax-checked; failed provisioning cleans up through the
account-deletion path; inactive provisioning invalidates caches
- Reconcile watermark advances only on a completed pass
- Wrapped orchestration errors keep their SCIM status; revoke audit names
the connection; group members show their display name
- UI: error state on the settings read, activity polls; SCIM reachable for
admins who did not configure SSO; docs wording on keys and cookies
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/scim.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ It pairs with [SSO](/platform/enterprise/sso). SSO proves who someone is when th
22
22
| --- | --- |
23
23
| Assigns a person to the Sim app | Creates their account and adds them to your organization as a Member |
24
24
| Updates their name or email | Updates the Sim account, and ends their sessions if the address changed |
25
-
| Deactivates them | Blocks sign-in and stops their API keys. Everything they own, and every grant they hold, is left untouched |
25
+
| Deactivates them | Blocks sign-in and stops their personal API keys. Everything they own, and every grant they hold, is left untouched; shared workspace keys keep working|
26
26
| Reactivates them | Restores access exactly as it was |
27
27
| Removes them from the app | Removes their organization membership and reassigns what they owned |
28
28
| Adds them to a group | Grants whatever that group maps to |
@@ -156,7 +156,7 @@ Sim also re-applies every group mapping on a schedule, so drift cannot persist.
156
156
<FAQitems={[
157
157
{
158
158
question: "What happens to someone's workflows when they are deactivated?",
159
-
answer: "Nothing. A deactivation blocks sign-in and stops their API keys, and leaves every workspace, workflow, and credential they own exactly as it was. Reactivating them restores access. Only a removal — which your provider sends explicitly — reassigns what they owned. A deactivated member also keeps their seat until they are removed."
159
+
answer: "Nothing. A deactivation blocks sign-in and stops their personal API keys, and leaves every workspace, workflow, and credential they own exactly as it was. Reactivating them restores access. Only a removal — which your provider sends explicitly — reassigns what they owned. A deactivated member also keeps their seat until they are removed."
160
160
},
161
161
{
162
162
question: "Can the directory provision someone outside our verified domains?",
@@ -176,7 +176,7 @@ Sim also re-applies every group mapping on a schedule, so drift cannot persist.
176
176
},
177
177
{
178
178
question: "Does a deactivation sign someone out immediately?",
179
-
answer: "Their sessions are deleted at once and their API keys stop authenticating immediately. A browser tab holding a cached session cookie can survive up to five minutes; enabling a session policy shortens that window."
179
+
answer: "Their sessions are deleted at once and their personal API keys stop authenticating immediately. The organization's security version changes at the same time, so a browser still holding a cached session cookie is re-checked on its next request and refused."
0 commit comments