Provider · Auth

WorkOS — Ashlr Stack Provider

WorkOS: Enterprise SSO + Directory Sync. API key verified via GET /organizations. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

Auth · API key KEY-ONLY · supplied credential attachment

WorkOS — Enterprise SSO + Directory Sync. API key verified via GET /organizations.

Dashboard ↗

One command

Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results.

stack add workos

Or retrieve catalog matches for what you're building via stack recommend:

stack recommend "drop-in user auth for my app"

Auth flow

Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed.

How-to: Find your API key and client ID in the WorkOS dashboard → API Keys.

Secret slots

stack add workos has these 2 catalog secret slots; verify which values its adapter actually materializes through Phantom:

WORKOS_API_KEY
WORKOS_CLIENT_ID

Use stack env export --example for an empty-key skeleton. Stack does not automatically fill env files or resolve credential placeholders. stack exec -- <cmd> forwards to installed Phantom exec; configure and verify the app separately.

Auth0 — Identity platform. Current adapter checks a domain's discovery endpoint and stores only the domain.
Clerk — Drop-in auth + users. Secret key stored in Phantom.

FAQ

Do I need a WorkOS account to use it with Stack?

Use an existing WorkOS account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed. If you don't have a credential yet, create one at https://dashboard.workos.com and supply the required inputs; inspect verification and persistence results.

Where does Stack store my WorkOS credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (WORKOS_API_KEY, WORKOS_CLIENT_ID); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.

Can I rotate or revoke this integration later?

Use `stack remove workos` for local WorkOS configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying WorkOS credentials through https://dashboard.workos.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.