Threetone has identity-event processing and directory-related membership fields, but no released self-service SCIM setup or verified end-to-end provisioning rollout. There is no documented Threetone tenant-URL and token wizard to follow.
Prepare the directory plan
You need the directory administrator, workspace owner, a small test cohort, and an agreed authority for identities and group membership. WorkOS directory provisioning requires organization-specific setup; provider capability alone does not activate it in Threetone.1
Define authoritative identities
Record stable user identifiers, primary emails, group IDs, and the intended workspace. Decide how contractors, duplicate emails, renamed users, and existing manual memberships should be handled.
2
Specify mappings and credentials
Document the intended user and group mappings. Obtain endpoint and credential details only through the supported setup process. Store provisioning credentials securely and identify their rotation owner.
3
Verify the complete lifecycle
Once provisioning is supported, test creation, attribute updates, group addition and removal, suspension, and reactivation. Inspect workspace membership, resource access, and existing-session behavior after each change. Record delayed or failed synchronization separately.
Does disabling SSO remove a workspace member?
Does disabling SSO remove a workspace member?
Do not assume it. Authentication, membership status, resource grants, and active sessions need separate verification.