docs(single-sign-on): clarify per-org Entity ID/ACS URL via WorkOS portal#1518
Merged
george-dilthey merged 3 commits intoJul 13, 2026
Merged
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Added a new subsection
### SAML configuration details (Entity ID and ACS URL)todocs/single-sign-on.md, under the "Setting up SSO" section. It explains that Clay's SAML Entity ID and ACS URL are unique per organization (not universal/static values), where to find them in the WorkOS setup portal (Service Provider Details section), and the SAML attribute requirements (email is the only required attribute; firstName, lastName, id are optional).Why
An Enterprise customer (Rob Mackay, Hyve Group) opened an Intercom ticket asking for "Clay's Entity ID and ACS URL" to configure an enterprise SSO application manually — the standard SAML setup approach where the SP publishes fixed metadata values. Fin escalated because its guidance said to route SSO questions to humans ("[Security] How to handle SSO questions"). The human agent (Amin Said) explained that Clay uses WorkOS, which generates org-specific SAML values via a setup link — customers don't look up universal Entity ID/ACS URL values. The docs' existing "Setting up SSO" steps described the WorkOS configuration link but didn't explain what it provides or where to find the SAML details, leaving this gap.
Source link(s)
/workspace/clay-base/apps/api/v3/auth/utils/SSOStrategy.tsconfirms WorkOS is the live SSO provider with per-org organization IDs; grep across the codebase found zero hardcoded SAML Entity ID or ACS URL values (verifier sub-agent, PASS verdict)Uncertainties
None. The verifier returned PASS with file:line evidence that WorkOS manages per-org SAML values dynamically, confirmed by two independent Slack threads from Clay staff.
Related observations
PR #1506 (#1506) is also open on
docs/single-sign-on.mdand adds SSO verification instructions (how to confirm SSO is active in an incognito window). That change is materially distinct from this one — the Entity ID/ACS URL explanation is absent from both the current doc and from PR #1506. A reviewer should reconcile these two PRs at merge time to avoid conflicts.Closes DOC-1098