# WorkOS

News about enterprise readiness from WorkOS.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Sync Engine: Mirror WorkOS data into your database

DevFeed: [Sync Engine: Mirror WorkOS data into your database](<https://devfeed.tech/articles/sync-engine-mirror-workos-data-into-your-database-146297.md>)

Original publisher: [Read original article](<https://workos.com/blog/sync-engine>)

Author: WorkOS

Published: 2026-11-19T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [rdbms](<https://devfeed.tech/topics/rdbms.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [etl](<https://devfeed.tech/topics/etl.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agent](<https://devfeed.tech/tags/ai-coding-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bi-tools](<https://devfeed.tech/tags/bi-tools.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [identity](<https://devfeed.tech/tags/identity.md>), [mirror](<https://devfeed.tech/tags/mirror.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [query](<https://devfeed.tech/tags/query.md>), [records](<https://devfeed.tech/tags/records.md>), [sync](<https://devfeed.tech/tags/sync.md>), [users](<https://devfeed.tech/tags/users.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS Sync Engine mirrors users, organizations, memberships, permissions, and emitted events into a database you control, letting applications join identity records with their own data in one database query. It supports Postgres, MySQL, MongoDB, and ClickHouse; generated `_live` views omit tombstoned rows, while retained deletion records can support investigation of departures within the records the mirror captured and still retains. Joins should include `_env` because IDs are unique per environment. Install `@workos/sync-engine` and a destination package, run it as a TypeScript library or Docker service, backfill existing records, keep the Events API poller running, and schedule reconciliation separately for supported streams. Polling and database write frequency are configurable within API rate limits. Permissions can be read alongside application data, but access decisions remain on the session token.

### Source excerpt

The WorkOS Sync Engine mirrors users, organizations, and memberships into your database, so you can query identity data alongside your application records.

## Agent Vault gives your agents a signed-in browser for websites without APIs

DevFeed: [Agent Vault gives your agents a signed-in browser for websites without APIs](<https://devfeed.tech/articles/agent-vault-gives-your-agents-a-signed-in-browser-for-websites-without-apis-140649.md>)

Original publisher: [Read original article](<https://workos.com/blog/agent-vault>)

Author: WorkOS

Published: 2026-11-17T00:00:00Z

Content type: release

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Agent Browser](<https://devfeed.tech/topics/agent-browser.md>), [agentic browsing](<https://devfeed.tech/topics/agentic-browsing.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [browser](<https://devfeed.tech/tags/browser.md>), [build](<https://devfeed.tech/tags/build.md>), [connect](<https://devfeed.tech/tags/connect.md>), [hosted](<https://devfeed.tech/tags/hosted.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [store](<https://devfeed.tech/tags/store.md>), [users](<https://devfeed.tech/tags/users.md>), [vault](<https://devfeed.tech/tags/vault.md>), [website](<https://devfeed.tech/tags/website.md>), [websites](<https://devfeed.tech/tags/websites.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

Agent Vault lets an agent work in a user-authenticated browser on websites without a usable API. Users save logins through a WorkOS widget; Agent Vault handles sign-in and keeps saved passwords out of the agent's prompts and tool responses. Agents connect through MCP to a hosted browser, while users can take over to complete steps such as SSO, CAPTCHA, or passkey checks and return the session. Developers can use the WorkOS-hosted browser or provide one through an existing browser integration; only one browser provider can be chosen per environment. Pipes provides OAuth tokens for supported integrations, while Agent Vault serves browser-only sites, and an application can use both. Access is enabled by the WorkOS team and the product is not generally available.

### Source excerpt

Build agentic products with Agent Vault: store users' website logins and connect agents through a WorkOS-hosted or self-hosted browser. Contact us for access.

## How your MCP server should call your API on the user's behalf

DevFeed: [How your MCP server should call your API on the user's behalf](<https://devfeed.tech/articles/how-your-mcp-server-should-call-your-api-on-the-user-s-behalf-140650.md>)

Original publisher: [Read original article](<https://workos.com/blog/mcp-server-call-api-on-behalf-of-user>)

Author: WorkOS

Published: 2026-11-17T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [API](<https://devfeed.tech/topics/api.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [trust](<https://devfeed.tech/topics/trust.md>), [A Minimal View for Token Exchange](<https://devfeed.tech/topics/a-minimal-view-for-token-exchange.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [act](<https://devfeed.tech/tags/act.md>), [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [cimd](<https://devfeed.tech/tags/cimd.md>), [claude](<https://devfeed.tech/tags/claude.md>), [client](<https://devfeed.tech/tags/client.md>), [connect](<https://devfeed.tech/tags/connect.md>), [consent](<https://devfeed.tech/tags/consent.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [error](<https://devfeed.tech/tags/error.md>), [errors](<https://devfeed.tech/tags/errors.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [token](<https://devfeed.tech/tags/token.md>), [token-exchange](<https://devfeed.tech/tags/token-exchange.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

An MCP server should exchange the user's MCP access token for a token scoped to the API, rather than forward the original: its audience is the MCP server, so the API should reject it. In WorkOS Connect, the server needs a first-party application with a client secret, both services registered as Resource Indicators, and token exchange enabled. It posts the user's eligible access token to `/oauth2/token`, naming the API URL as `resource`; it may request narrower scopes, which cannot be widened. The returned token keeps the user and organization, sets the API as `aud`, and records the exchanging app in `act`. The API should verify the signature, issuer, audience, actor and required scopes. The response includes no refresh or ID token and expires no later than the source token, so the server must exchange again when needed. Introspection can check current token status, but does not validate audience or return `act`; those claims still require separate checks. This overview reflects the supplied body text.

### Source excerpt

Use WorkOS Connect token exchange to swap the user's MCP token for one scoped to your API, then check the claims your API needs to trust it.

## SCIM: Let your customers debug your integrations

DevFeed: [SCIM: Let your customers debug your integrations](<https://devfeed.tech/articles/scim-let-your-customers-debug-your-integrations-131820.md>)

Original publisher: [Read original article](<https://workos.com/blog/customer-facing-scim-integration-logs>)

Author: WorkOS

Published: 2026-11-12T00:00:00Z

Content type: opinion

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Support](<https://devfeed.tech/topics/support.md>), [API Economy](<https://devfeed.tech/topics/api-economy.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [act](<https://devfeed.tech/tags/act.md>), [active-directory](<https://devfeed.tech/tags/active-directory.md>), [admin](<https://devfeed.tech/tags/admin.md>), [also](<https://devfeed.tech/tags/also.md>), [building](<https://devfeed.tech/tags/building.md>), [can](<https://devfeed.tech/tags/can.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [debug](<https://devfeed.tech/tags/debug.md>), [failure](<https://devfeed.tech/tags/failure.md>), [integration](<https://devfeed.tech/tags/integration.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [it](<https://devfeed.tech/tags/it.md>), [let](<https://devfeed.tech/tags/let.md>), [logs](<https://devfeed.tech/tags/logs.md>), [support](<https://devfeed.tech/tags/support.md>), [ticket](<https://devfeed.tech/tags/ticket.md>)

### AI overview

Customer-facing SCIM logs can let IT admins diagnose provisioning failures themselves by showing the request and response that crossed the integration boundary, rather than relying on support summaries. The article's design exposes write requests scoped to the customer's directory, redacts sensitive values, translates failures into next steps, supports practical filters, and links requests to resulting events; reads are omitted to avoid polling noise. Its example shows an admin spotting an empty `userName` field and correcting the IdP mapping--or identifying an issue to take to Okta. Logs are retained for 30 days, which the article says may be shorter than some escalations. The same visibility approach is suggested for other customer-configured integrations, including SSO, webhooks, and data imports.

### Source excerpt

When the person who can fix an integration can't see it, every failure becomes a support ticket. Why integration logs belong in front of the customer, and what we learned building them for SCIM.

## SSO sign-in consent screen: What it is and how to handle denials

DevFeed: [SSO sign-in consent screen: What it is and how to handle denials](<https://devfeed.tech/articles/sso-sign-in-consent-screen-what-it-is-and-how-to-handle-denials-127144.md>)

Original publisher: [Read original article](<https://workos.com/blog/sso-sign-in-consent-screen>)

Author: WorkOS

Published: 2026-11-10T16:15:34Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Exception handling](<https://devfeed.tech/topics/exception-handling.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>)

Tags: [branding](<https://devfeed.tech/tags/branding.md>), [callback](<https://devfeed.tech/tags/callback.md>), [consent](<https://devfeed.tech/tags/consent.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

WorkOS's SSO consent screen appears after identity-provider authentication and before the app receives an authorization code, showing the returned email and provider origin for user confirmation. Approval is remembered per user; the screen is enabled by default in new environments, while older ones should be checked in Authentication settings. Handle `signin_consent_denied` before expecting a code: direct the user to contact their admin and support about a possible phishing attempt, and keep this distinct from `access_denied`. For IdP-initiated logins, consent appears until approval; a configured sign-in endpoint can route the login into a standard SP-initiated flow and includes `connection_id`. Review the applicable environment branding, colors, and logos, since sandbox branding does not predict production. The screen adds a deliberate user check alongside other defenses, but cannot verify the displayed identity for the user.

### Source excerpt

The sign-in consent screen shows users their email and identity provider before SSO completes. When it appears, how to handle a denial, and what to brand.

## How to add authentication to a Rust axum app with WorkOS AuthKit

DevFeed: [How to add authentication to a Rust axum app with WorkOS AuthKit](<https://devfeed.tech/articles/how-to-add-authentication-to-a-rust-axum-app-with-workos-authkit-123473.md>)

Original publisher: [Read original article](<https://workos.com/blog/rust-axum-authentication-authkit>)

Author: WorkOS

Published: 2026-11-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Rust](<https://devfeed.tech/topics/rust.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [client library](<https://devfeed.tech/topics/client-library.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [request](<https://devfeed.tech/tags/request.md>), [rust](<https://devfeed.tech/tags/rust.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [service](<https://devfeed.tech/tags/service.md>), [webhook](<https://devfeed.tech/tags/webhook.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

The WorkOS Rust SDK lets an axum service authenticate with AuthKit using sealed session cookies and locally verified access tokens. The source outlines the flow: build and share a client, create a PKCE authorization URL while storing the verifier and state in a short-lived sealed cookie, exchange the callback code, then authenticate the session on each request. Cookie passwords must be 64-character hex strings; the Rust cookie format is not compatible with other WorkOS SDKs. Local verification fetches and caches signing keys, but cannot detect session revocation until the access token expires, so the source recommends webhook handling and rechecks before destructive operations when revocation matters. For webhooks, verify the signature against the timestamp and exact raw body before parsing; deliveries may repeat or arrive out of order, so record processed event IDs and return 200 promptly. SDK retries cover 429s, 5xxs and retryable transport errors, but unsafe HTTP methods retry only when given an idempotency key--and only if the endpoint deduplicates it.

### Source excerpt

Use the WorkOS Rust SDK to sign users in with AuthKit, verify their session on every request, and check webhook signatures in an axum service.

## Black October 2026: How AI sped up bug hunting and attacks

DevFeed: [Black October 2026: How AI sped up bug hunting and attacks](<https://devfeed.tech/articles/black-october-2026-how-ai-sped-up-bug-hunting-and-attacks-123472.md>)

Original publisher: [Read original article](<https://workos.com/blog/black-october-2026-ai-security>)

Author: WorkOS

Published: 2026-11-09T00:00:00Z

Content type: news

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [ai-assisted attacks](<https://devfeed.tech/topics/ai-assisted-attacks.md>), [litellm attack](<https://devfeed.tech/topics/litellm-attack.md>), [litellm](<https://devfeed.tech/topics/litellm.md>), [Threat Hunting & Intel](<https://devfeed.tech/topics/threat-hunting-intel.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [all](<https://devfeed.tech/tags/all.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [black](<https://devfeed.tech/tags/black.md>), [black-october](<https://devfeed.tech/tags/black-october.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bug-hunting](<https://devfeed.tech/tags/bug-hunting.md>), [ca](<https://devfeed.tech/tags/ca.md>), [critical](<https://devfeed.tech/tags/critical.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [here-s](<https://devfeed.tech/tags/here-s.md>), [hit](<https://devfeed.tech/tags/hit.md>), [keys](<https://devfeed.tech/tags/keys.md>), [litellm](<https://devfeed.tech/tags/litellm.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [october](<https://devfeed.tech/tags/october.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [up](<https://devfeed.tech/tags/up.md>)

### AI overview

Black October's flaws came from familiar causes, while AI appears to have accelerated discovery and intrusions. PHP's October 21 releases fix two critical unauthenticated remote code execution bugs; the advisory says all web SAPIs are affected and updating is the only complete mitigation. Node.js patched 10 vulnerabilities, including a Brotli flaw later listed by CISA as actively exploited. GitLab patched a critical unauthenticated code execution issue; self-compiled installations also need updated Ruby. Chrome and Mozilla blocked affected eMudhra CA keys, and eMudhra said it would exit global SSL/TLS certificates. LiteLLM reported that a malicious package and Docker tags were briefly available; its account describes stolen developer tokens, exposed logs, and a release workflow compromise. Wiz says AI helped find and validate PHP exploits, though its claim that one researcher compressed months of work into a week lacks published metrics. ARTEX reports describe machine-speed intrusions, with Google noting a tradeoff between speed and stealth. The text says two of the five core disclosures had no reported AI involvement.

### Source excerpt

Critical flaws in PHP, Node.js and GitLab, a poisoned LiteLLM release and weak CA keys all hit in October 2026. Here's what AI had to do with it.

## SSO is broken? The answer is already in your session log

DevFeed: [SSO is broken? The answer is already in your session log](<https://devfeed.tech/articles/sso-is-broken-the-answer-is-already-in-your-session-log-124330.md>)

Original publisher: [Read original article](<https://workos.com/blog/sso-broken-session-log>)

Author: WorkOS

Published: 2026-11-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [log management](<https://devfeed.tech/topics/log-management.md>)

Tags: [configuration](<https://devfeed.tech/tags/configuration.md>), [customer](<https://devfeed.tech/tags/customer.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [events](<https://devfeed.tech/tags/events.md>), [failed](<https://devfeed.tech/tags/failed.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [it](<https://devfeed.tech/tags/it.md>), [sso](<https://devfeed.tech/tags/sso.md>), [status](<https://devfeed.tech/tags/status.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS session logs can pinpoint where an SSO failure occurs and who can fix it. In the dashboard, filter a connection's Sessions tab by email, status, origin or time, then inspect the IdP request, response and any error. Success shifts investigation to app handling or authorization; failed sessions may point to the IdP or to your attribute mapping. Required attributes that are missing can fail sign-in, while unmapped optional attributes return null and may leave a successful session with empty fields. Origin helps distinguish app-started, IdP-started and Admin Portal test flows; OIDC is SP-initiated only. For patterns, use SSO events with connection IDs and error details: stream them to Datadog or count failures by connection through the cursor-paginated Events API. When the IdP is responsible, share the session ID, timestamp, status and response with its administrator.

### Source excerpt

Every WorkOS SSO attempt records its status, origin and the IdP's response. Read it in five minutes and know whether the fix is yours or the customer's.

## How to add authentication to Next.js without creating an account

DevFeed: [How to add authentication to Next.js without creating an account](<https://devfeed.tech/articles/how-to-add-authentication-to-next-js-without-creating-an-account-123471.md>)

Original publisher: [Read original article](<https://workos.com/blog/add-authentication-nextjs-without-account>)

Author: WorkOS

Published: 2026-11-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [self-service](<https://devfeed.tech/topics/self-service.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [cli](<https://devfeed.tech/tags/cli.md>), [environment](<https://devfeed.tech/tags/environment.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

Run `npx workos@latest install` in a Next.js 15.3+ app to add AuthKit sign-in, sign-out, callback routing, and session handling without first creating a WorkOS account. With no existing `WORKOS_API_KEY`, the CLI provisions a temporary environment and writes credentials to `.env.local`; it detects the Next.js version and router, and keeps existing keys if found. Review the CLI's changes on its branch; it does not stage, commit, or push them. Unclaimed environments work for testing but expire after 7 days. To keep one, claim it through the CLI and WorkOS dashboard; claiming is permanent. Then log in to the CLI, remove `WORKOS_CLAIM_TOKEN`, and configure a separate production environment before shipping. The excerpt also describes agent mode, which avoids interactive prompts and supports JSON/NDJSON output and claim links. Setup requires a clean Git working tree.

### Source excerpt

Run one command to add sign-in to a Next.js app. The WorkOS CLI creates a temporary environment and writes your keys. Claim it when you want to keep it.

## How to handle SAML certificate expiration with WorkOS webhooks

DevFeed: [How to handle SAML certificate expiration with WorkOS webhooks](<https://devfeed.tech/articles/how-to-handle-saml-certificate-expiration-with-workos-webhooks-122040.md>)

Original publisher: [Read original article](<https://workos.com/blog/saml-certificate-expiration-webhooks>)

Author: WorkOS

Published: 2026-11-06T14:45:31Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [saml](<https://devfeed.tech/topics/saml.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [certificate](<https://devfeed.tech/tags/certificate.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [saml](<https://devfeed.tech/tags/saml.md>), [webhooks](<https://devfeed.tech/tags/webhooks.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS's SAML certificate events can drive one idempotent open reminder per connection, certificate type, and expiry date. Repeated or duplicate renewal notices update that reminder; route by `certificate_type`: `ResponseSigning` needs customer IT to replace the IdP certificate, while `RequestSigning` needs confirmation that the customer's IdP will pick up WorkOS's SP metadata rotation. Treat `connection.saml_certificate_renewed` as a prompt to inspect certificates for the connection, not proof the reminder can close; rotations for request signing may be silent. Escalate when `is_expired` is true. WorkOS IT contacts can receive renewal alerts and a task-scoped Admin Portal link, which expires after five minutes. Verify webhook signatures, acknowledge quickly and process asynchronously, and subscribe only to needed event types.

### Source excerpt

WorkOS sends an event before a SAML certificate expires. Turn it into one open reminder per certificate, routed to the person who can actually renew it.

## Why your Electron deep link works on macOS but not on Windows

DevFeed: [Why your Electron deep link works on macOS but not on Windows](<https://devfeed.tech/articles/why-your-electron-deep-link-works-on-macos-but-not-on-windows-122039.md>)

Original publisher: [Read original article](<https://workos.com/blog/electron-deep-links-macos-windows-linux>)

Author: WorkOS

Published: 2026-11-06T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Electron](<https://devfeed.tech/topics/electron.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [Windows](<https://devfeed.tech/topics/windows.md>), [Process](<https://devfeed.tech/topics/process.md>)

Tags: [deep](<https://devfeed.tech/tags/deep.md>), [electron](<https://devfeed.tech/tags/electron.md>), [link](<https://devfeed.tech/tags/link.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Electron delivers custom-scheme callbacks differently by platform: macOS sends an `open-url` event, while Windows and Linux launch a second process whose arguments reach the first instance through `second-instance`. For Windows and Linux, acquire `app.requestSingleInstanceLock()` early and find the URL by its scheme rather than assuming it is the last argument. Register the protocol inside `app.whenReady()` before creating a window; handle a closed-app launch from `process.argv` on Windows/Linux, and account for macOS cold-start listener timing. Packaged macOS and Linux builds also need scheme declarations in `Info.plist` and the Linux `.desktop` file; Windows registers at first app run, so an unopened install cannot be launched by a callback. The article says macOS and Linux links require packaging during development, and Linux session persistence needs an OS keyring; without one, the SDK refuses plaintext storage. Test packaged builds on all three platforms, including closed-app returns on Windows and Linux.

### Source excerpt

macOS hands a custom-scheme URL to the running app. Windows and Linux start a second copy with the URL in its arguments. Here is the main-process code for both.

## Flip a feature flag from your own workflow with the WorkOS API

DevFeed: [Flip a feature flag from your own workflow with the WorkOS API](<https://devfeed.tech/articles/flip-a-feature-flag-from-your-own-workflow-with-the-workos-api-121080.md>)

Original publisher: [Read original article](<https://workos.com/blog/feature-flag-targets-api>)

Author: WorkOS

Published: 2026-11-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [automation](<https://devfeed.tech/tags/automation.md>), [billing](<https://devfeed.tech/tags/billing.md>), [crm](<https://devfeed.tech/tags/crm.md>), [feature-flags](<https://devfeed.tech/tags/feature-flags.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [target](<https://devfeed.tech/tags/target.md>), [users](<https://devfeed.tech/tags/users.md>), [workflow](<https://devfeed.tech/tags/workflow.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS targeting endpoints let server-side workflows grant or revoke a feature for an organization or user: POST adds a target and DELETE removes it in the API key's environment. Removal restores the flag's default value, so per-customer access should use a false default if deletion is meant to revoke access. For CRM or billing webhooks, keep the API key server-side, make retries idempotent using event IDs, return failures for provider retries, and log the event, target, flag, actor and time. Changes reach users through their existing session: feature_flags claims update at sign-in or session refresh and count toward a 3,072-byte token limit; the Node runtime client keeps flags out of the token and syncs in the background every 30 seconds by default, requiring @workos-inc/node 12 or later to confirm changes.

### Source excerpt

Use the WorkOS Feature Flags targeting endpoints to add and remove organizations and users from your own systems, and learn what removing a target really does.

## Per-workspace roles: Custom roles scoped to a resource type in WorkOS

DevFeed: [Per-workspace roles: Custom roles scoped to a resource type in WorkOS](<https://devfeed.tech/articles/per-workspace-roles-custom-roles-scoped-to-a-resource-type-in-workos-121082.md>)

Original publisher: [Read original article](<https://workos.com/blog/resource-scoped-custom-roles>)

Author: WorkOS

Published: 2026-11-05T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [custom](<https://devfeed.tech/tags/custom.md>), [organization](<https://devfeed.tech/tags/organization.md>), [resource](<https://devfeed.tech/tags/resource.md>), [roles](<https://devfeed.tech/tags/roles.md>), [type](<https://devfeed.tech/tags/type.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

Resource-scoped WorkOS roles let one organization member have different access on individual workspaces or projects, avoiding organization-wide roles for every access combination. Define resource types in the Dashboard, scope permissions and roles to the matching type, assign a role to a membership on a specific resource, and use authorization endpoints to check access; project permissions can inherit through a workspace. Environment roles suit permissions shared across customers, while custom roles belong to one organization. Resource types, role scopes, permission scopes, and slugs are immutable, so correcting a scope requires creating replacements, migrating assignments and application checks, then deleting old entries. The text also notes hierarchy and instance limits, role slug rules, and deletion conflicts while assignments or group mappings remain.

### Source excerpt

Organization roles give a member the same access everywhere. Scope a WorkOS role to a resource type and one person can edit one workspace and view another.

## Stream your customers' audit logs into their own Snowflake warehouse

DevFeed: [Stream your customers' audit logs into their own Snowflake warehouse](<https://devfeed.tech/articles/stream-your-customers-audit-logs-into-their-own-snowflake-warehouse-121079.md>)

Original publisher: [Read original article](<https://workos.com/blog/audit-log-streaming-snowflake>)

Author: WorkOS

Published: 2026-11-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Snowflake streaming data architecture](<https://devfeed.tech/topics/snowflake-streaming-data-architecture.md>), [audit](<https://devfeed.tech/topics/audit.md>), [stream-processing](<https://devfeed.tech/topics/stream-processing.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [auth](<https://devfeed.tech/tags/auth.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [event](<https://devfeed.tech/tags/event.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [key](<https://devfeed.tech/tags/key.md>), [logs](<https://devfeed.tech/tags/logs.md>), [pair](<https://devfeed.tech/tags/pair.md>), [schema](<https://devfeed.tech/tags/schema.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [stream](<https://devfeed.tech/tags/stream.md>), [table](<https://devfeed.tech/tags/table.md>), [up](<https://devfeed.tech/tags/up.md>), [warehouse](<https://devfeed.tech/tags/warehouse.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

WorkOS Log Streams can write each organization's audit events as rows in the customer's own Snowflake account, where the customer controls storage and retention. Setup requires a dedicated user authenticated by an RSA key pair, a table with the documented schema, and a default role granted access to the warehouse, database, schema, and table; accounts with network policies must allow WorkOS's published IP addresses. The dashboard and Admin Portal configure the same stream, but the portal lets the customer provide credentials directly so the private key need not pass through support. Monitor actual delivery with a customer-specific freshness query in Snowflake: an Active state alone does not establish that rows are arriving, and the article says not to assume stop-delivery notifications. Error or Invalid streams require fixing the cause and revalidating. Delivery resumes from the last successful event, subject to the organization's WorkOS retention window; previously delivered rows remain subject to the customer's own warehouse policy.

### Source excerpt

Each audit event lands as a row in your customer's own Snowflake table, with key-pair auth, a fixed schema, grants up front, and a freshness check.

## Let each customer bring their own OAuth app with WorkOS Pipes

DevFeed: [Let each customer bring their own OAuth app with WorkOS Pipes](<https://devfeed.tech/articles/let-each-customer-bring-their-own-oauth-app-with-workos-pipes-121081.md>)

Original publisher: [Read original article](<https://workos.com/blog/pipes-bring-your-own-oauth-app>)

Author: WorkOS

Published: 2026-11-05T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [backend](<https://devfeed.tech/tags/backend.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [custom](<https://devfeed.tech/tags/custom.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [data-integration](<https://devfeed.tech/tags/data-integration.md>), [docs](<https://devfeed.tech/tags/docs.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [secret](<https://devfeed.tech/tags/secret.md>), [widget](<https://devfeed.tech/tags/widget.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS Pipes organization credentials let each customer register and control its own OAuth app. This is configured per provider for the whole environment: once enabled, every organization must supply a client ID and secret before its members can connect. Admins can configure credentials through the permission-gated PipesAdmin widget or API; members use the standard Pipes widget, and each member still authorizes a personal connection scoped to their organization. Setup requires creating the OAuth app, registering Pipes' redirect URI, saving the credential pair, choosing scopes, and enabling the provider. Rotation replaces the stored secret; retirement happens in the provider's console, while disabling a provider only hides it from that organization's members. The excerpt notes there is no documented remove-credentials control and no Node SDK method for the configuration API.

### Source excerpt

When a provider needs each customer's own OAuth app, the Pipes Admin widget lets their admin register it, rotate the secret and retire it without your help.

## How to set up AD FS SAML SSO: Relying party trust, claims rules and metadata

DevFeed: [How to set up AD FS SAML SSO: Relying party trust, claims rules and metadata](<https://devfeed.tech/articles/how-to-set-up-ad-fs-saml-sso-relying-party-trust-claims-rules-and-metadata-117622.md>)

Original publisher: [Read original article](<https://workos.com/blog/adfs-saml-sso-setup>)

Author: WorkOS

Published: 2026-11-04T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [saml](<https://devfeed.tech/topics/saml.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2016](<https://devfeed.tech/tags/2016.md>), [2019](<https://devfeed.tech/tags/2019.md>), [2022](<https://devfeed.tech/tags/2022.md>), [cause](<https://devfeed.tech/tags/cause.md>), [console](<https://devfeed.tech/tags/console.md>), [details](<https://devfeed.tech/tags/details.md>), [failed](<https://devfeed.tech/tags/failed.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [party](<https://devfeed.tech/tags/party.md>), [plus](<https://devfeed.tech/tags/plus.md>), [rules](<https://devfeed.tech/tags/rules.md>), [saml](<https://devfeed.tech/tags/saml.md>), [set](<https://devfeed.tech/tags/set.md>), [sign](<https://devfeed.tech/tags/sign.md>), [sso](<https://devfeed.tech/tags/sso.md>), [trust](<https://devfeed.tech/tags/trust.md>), [up](<https://devfeed.tech/tags/up.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

An AD FS SAML connection requires an administrator to create a claims-aware relying party trust from WorkOS SP metadata, configure claims, and provide AD FS federation metadata to WorkOS. Verify the trust's SAML Assertion Consumer Endpoint matches the connection's ACS URL. The LDAP claims rule should send email and UPN: email is required on the WorkOS profile, while the UPN supplies the AD FS user identifier. Given name and surname are optional and may be null if omitted. Groups are optional for sign-in but needed for group-based role assignment; configure role mappings and test with a user in a mapped group. Group changes reach the app at that user's next SSO sign-in. Alternatively, Directory Sync group-based assignment avoids those limits, and the excerpt recommends using one method. Federation metadata can be entered as a URL or uploaded as XML; file upload requires refreshing it when the signing certificate changes.

### Source excerpt

A step-by-step walkthrough of the AD FS console work behind a SAML SSO connection, plus the claims and metadata details that cause failed sign-ins later.

## IdP-initiated SSO: How to turn a dashboard tile click into a normal sign-in

DevFeed: [IdP-initiated SSO: How to turn a dashboard tile click into a normal sign-in](<https://devfeed.tech/articles/idp-initiated-sso-how-to-turn-a-dashboard-tile-click-into-a-normal-sign-in-117625.md>)

Original publisher: [Read original article](<https://workos.com/blog/idp-initiated-sso-sign-in-endpoint>)

Author: WorkOS

Published: 2026-11-04T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [callback](<https://devfeed.tech/tags/callback.md>), [code](<https://devfeed.tech/tags/code.md>), [configure](<https://devfeed.tech/tags/configure.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [domain](<https://devfeed.tech/tags/domain.md>), [email](<https://devfeed.tech/tags/email.md>), [flask](<https://devfeed.tech/tags/flask.md>), [http](<https://devfeed.tech/tags/http.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [idp](<https://devfeed.tech/tags/idp.md>), [localhost](<https://devfeed.tech/tags/localhost.md>), [login](<https://devfeed.tech/tags/login.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [sso](<https://devfeed.tech/tags/sso.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

For IdP-initiated SAML, WorkOS can redirect a dashboard tile click to your app's sign-in endpoint with a `connection_id`; your endpoint then calls Get Authorization URL and starts an ordinary SP-initiated flow. Configure the endpoint and allowed redirect URIs in the WorkOS Dashboard; production redirect URIs cannot use HTTP or localhost. The callback remains the usual authorization-code exchange, and the returned profile's organization ID should still be validated. Without a sign-in endpoint, the authorization code goes to the app's default redirect URI, and tenant routing must wait until the profile reveals its `connection_id`. RelayState can include a `client_id` to route to a particular application's endpoint. IdP-initiated login applies only to SAML; OIDC remains SP-initiated.

### Source excerpt

Configure a sign-in endpoint and WorkOS turns an identity provider tile click into a normal SP-initiated sign-in, handing your app the connection_id it needs.

## Send your own AuthKit emails: Invitations, Magic Auth, verification and password reset

DevFeed: [Send your own AuthKit emails: Invitations, Magic Auth, verification and password reset](<https://devfeed.tech/articles/send-your-own-authkit-emails-invitations-magic-auth-verification-and-password-reset-117623.md>)

Original publisher: [Read original article](<https://workos.com/blog/authkit-custom-emails>)

Author: WorkOS

Published: 2026-11-04T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [email](<https://devfeed.tech/topics/email.md>), [password reset](<https://devfeed.tech/topics/password-reset.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [passwords](<https://devfeed.tech/topics/passwords.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [acceptance](<https://devfeed.tech/tags/acceptance.md>), [account](<https://devfeed.tech/tags/account.md>), [admin](<https://devfeed.tech/tags/admin.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [api](<https://devfeed.tech/tags/api.md>), [auth](<https://devfeed.tech/tags/auth.md>), [email](<https://devfeed.tech/tags/email.md>), [email-verification](<https://devfeed.tech/tags/email-verification.md>), [magic](<https://devfeed.tech/tags/magic.md>), [one](<https://devfeed.tech/tags/one.md>), [password](<https://devfeed.tech/tags/password.md>), [password-reset](<https://devfeed.tech/tags/password-reset.md>), [reset](<https://devfeed.tech/tags/reset.md>), [send](<https://devfeed.tech/tags/send.md>), [turning](<https://devfeed.tech/tags/turning.md>), [verification](<https://devfeed.tech/tags/verification.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Turning off AuthKit's default emails applies across an entire environment and leaves you responsible for invitation, Magic Auth, email verification, and password reset messages. For objects created outside your backend, subscribe to the corresponding events, retrieve each full object through its get endpoint because event payloads omit the secret, then email its address with the code or link. API-created objects return the needed values directly. Invitations require both `invitation.created` and `invitation.resent`; manually sent invitations also need event handling. Email verification remains on, and invited users who sign up with a password must verify when WorkOS did not email the invitation. Hosted AuthKit pages use default invitation and reset URLs; custom pages must capture and process the relevant token. Test in staging, account for Dashboard and hosted UI flows, and handle localization yourself. The article notes that Custom Email Providers may be a smaller option when only the sending domain or provider needs to change.

### Source excerpt

Turning off AuthKit's default emails is one setting. The work is the four flows you then own: invitations, Magic Auth, email verification and password reset.

## GitHub App installation tokens are now 520 characters: What to check before November 30

DevFeed: [GitHub App installation tokens are now 520 characters: What to check before November 30](<https://devfeed.tech/articles/github-app-installation-tokens-are-now-520-characters-what-to-check-before-november-30-117624.md>)

Original publisher: [Read original article](<https://workos.com/blog/github-app-installation-token-format-change>)

Author: WorkOS

Published: 2026-11-04T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [GitHub API](<https://devfeed.tech/topics/github-api.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [actions](<https://devfeed.tech/tags/actions.md>), [api](<https://devfeed.tech/tags/api.md>), [audit](<https://devfeed.tech/tags/audit.md>), [automation](<https://devfeed.tech/tags/automation.md>), [config](<https://devfeed.tech/tags/config.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [data-residency](<https://devfeed.tech/tags/data-residency.md>), [database](<https://devfeed.tech/tags/database.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [format](<https://devfeed.tech/tags/format.md>), [github](<https://devfeed.tech/tags/github.md>), [header](<https://devfeed.tech/tags/header.md>), [installation](<https://devfeed.tech/tags/installation.md>), [override](<https://devfeed.tech/tags/override.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

GitHub App installation tokens are now variable-length, about 520-character `ghs_` strings by default; their permissions, repository scope, and one-hour expiry remain unchanged. The change affects installation server-to-server tokens, including Actions `GITHUB_TOKEN`, on GitHub Enterprise Cloud and Data Residency; GitHub Enterprise Server is excluded. Audit token validation and redaction patterns, storage limits, and every proxy or gateway that handles `Authorization` headers. Test redaction with a real stateless token and send one end to end to verify it reaches the origin intact. Until November 30, 2026, `X-GitHub-Stateless-S2S-Token` can select stateless (`enabled`) or classic (`disabled`) format for an issuance request; other values are ignored. After that date the header is no longer respected, and eligible apps receive stateless tokens. Treat tokens as opaque strings rather than parsing their JWT contents. The excerpt says `ghu_` user tokens are not currently in scope, while noting future format changes have not been ruled out.

### Source excerpt

GitHub App installation tokens are now about 520 characters instead of 40. What to audit before the override header is deprecated on November 30, 2026.

## SSO just-in-time provisioning: How to match a login to an existing user safely

DevFeed: [SSO just-in-time provisioning: How to match a login to an existing user safely](<https://devfeed.tech/articles/sso-just-in-time-provisioning-how-to-match-a-login-to-an-existing-user-safely-117626.md>)

Original publisher: [Read original article](<https://workos.com/blog/sso-jit-provisioning-account-matching>)

Author: WorkOS

Published: 2026-11-04T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [attack](<https://devfeed.tech/tags/attack.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [branch](<https://devfeed.tech/tags/branch.md>), [callback](<https://devfeed.tech/tags/callback.md>), [condition](<https://devfeed.tech/tags/condition.md>), [email](<https://devfeed.tech/tags/email.md>), [just](<https://devfeed.tech/tags/just.md>), [login](<https://devfeed.tech/tags/login.md>), [order](<https://devfeed.tech/tags/order.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>), [safely](<https://devfeed.tech/tags/safely.md>), [sso](<https://devfeed.tech/tags/sso.md>), [store](<https://devfeed.tech/tags/store.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

For a custom SSO callback, resolve an existing identity first using the persistent `idp_id` scoped to its connection; if none exists, link by email only when the connection's organization has verified the email domain or an authoritative identity provider asserts a verified address. Otherwise create a separate user or require inbox proof before linking. Store the identity separately from the user, key it by the `idp_id` and connection pair, and refresh mutable profile attributes on returning sign-ins. Scope email lookups deliberately because a global match may belong to another customer. WorkOS's domain check blocks nonmatching profiles by default, but the callback should still enforce its own linking condition. The excerpt says AuthKit follows a similar link-first, verified-email, then create order, with verification and guest-invitation behavior handled in its flow.

### Source excerpt

Just-in-time provisioning is a resolution order in your SSO callback. Here is the order, the condition that makes the email match safe, and what to store.

## Evaluate feature flags locally in Node with the WorkOS runtime client

DevFeed: [Evaluate feature flags locally in Node with the WorkOS runtime client](<https://devfeed.tech/articles/evaluate-feature-flags-locally-in-node-with-the-workos-runtime-client-117627.md>)

Original publisher: [Read original article](<https://workos.com/blog/workos-feature-flags-node-runtime-client>)

Author: WorkOS

Published: 2026-11-04T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [client library](<https://devfeed.tech/topics/client-library.md>)

Tags: [feature-flags](<https://devfeed.tech/tags/feature-flags.md>), [node](<https://devfeed.tech/tags/node.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

The WorkOS Node runtime client evaluates feature flags locally from in-memory configuration and syncs with the Dashboard in the background, avoiding network waits on checks and supporting jobs or webhooks without user sessions. It is available in the Node SDK from v12.0.0 and requires Node 22.11 or later; use a shared client, attach an error listener, and decide whether startup should wait for readiness or use bootstrap flags. Before data arrives, unknown flags return false or a supplied default. The default polling interval is 30 seconds (minimum five); recoverable sync errors retain the last configuration, while invalid credentials stop syncing until the client is recreated. Small, stable flag sets in authenticated requests can instead use the access-token claim, which updates on sign-in or session refresh and shares a 3,072-byte limit with other claims.

### Source excerpt

The WorkOS Node SDK ships a feature flags runtime client that keeps flag configuration in memory, so a flag check on a hot path never waits on a request.

## Let your customer's IT admin manage team members inside your app

DevFeed: [Let your customer's IT admin manage team members inside your app](<https://devfeed.tech/articles/let-your-customer-s-it-admin-manage-team-members-inside-your-app-115974.md>)

Original publisher: [Read original article](<https://workos.com/blog/users-management-widget-customer-admins>)

Author: WorkOS

Published: 2026-11-03T16:52:24Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [in-app experiences](<https://devfeed.tech/topics/in-app-experiences.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [actions](<https://devfeed.tech/tags/actions.md>), [admin](<https://devfeed.tech/tags/admin.md>), [app](<https://devfeed.tech/tags/app.md>), [b2b](<https://devfeed.tech/tags/b2b.md>), [can](<https://devfeed.tech/tags/can.md>), [change](<https://devfeed.tech/tags/change.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [inside](<https://devfeed.tech/tags/inside.md>), [it](<https://devfeed.tech/tags/it.md>), [it-admins](<https://devfeed.tech/tags/it-admins.md>), [let](<https://devfeed.tech/tags/let.md>), [manage](<https://devfeed.tech/tags/manage.md>), [members](<https://devfeed.tech/tags/members.md>), [roles](<https://devfeed.tech/tags/roles.md>), [team](<https://devfeed.tech/tags/team.md>), [ticket](<https://devfeed.tech/tags/ticket.md>), [widget](<https://devfeed.tech/tags/widget.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

The WorkOS `<UsersManagement />` React widget provides a members page for one organization, letting authorized admins list members, invite them, resend or revoke pending invitations, change roles, remove members, and filter by role. It requires `widgets:users-table:manage`, an all-or-nothing permission that is checked when the widget uses its token; test with a low-privilege role because successful token creation alone does not prove access. You can pass a server-created widget token scoped to an organization (it expires after one hour), or pass AuthKit's `getAccessToken` function when the access token is scoped to the displayed organization and includes the permission. Setup also requires `@workos-inc/widgets` and peer dependencies, a `WorkOsWidgets` provider, and an allowed web origin configured for CORS. Directory-managed members can have roles changed in the widget, but removal must happen in the identity provider; directory sync can also overwrite manually changed roles.

### Source excerpt

Drop the WorkOS UsersManagement widget into your B2B app so your customers' own IT admins can invite members, remove them, and change roles without a ticket.

## How to revoke an AI agent's access: Ending agent sessions in an organization

DevFeed: [How to revoke an AI agent's access: Ending agent sessions in an organization](<https://devfeed.tech/articles/how-to-revoke-an-ai-agent-s-access-ending-agent-sessions-in-an-organization-115972.md>)

Original publisher: [Read original article](<https://workos.com/blog/revoke-ai-agent-sessions>)

Author: WorkOS

Published: 2026-11-03T14:43:06Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Authorization](<https://devfeed.tech/topics/authorization.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>)

Tags: [acceptance](<https://devfeed.tech/tags/acceptance.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [account](<https://devfeed.tech/tags/account.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-auth](<https://devfeed.tech/tags/agent-auth.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [auth](<https://devfeed.tech/tags/auth.md>), [can](<https://devfeed.tech/tags/can.md>), [effect](<https://devfeed.tech/tags/effect.md>), [fast](<https://devfeed.tech/tags/fast.md>), [here](<https://devfeed.tech/tags/here.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [organization](<https://devfeed.tech/tags/organization.md>), [routine](<https://devfeed.tech/tags/routine.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [takes](<https://devfeed.tech/tags/takes.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS Agent Auth access is revoked at the session level. List sessions with `GET /agents/sessions`, filtering by organization, blueprint, or instance, and page through results; then revoke the appropriate session with `POST`. Revocation invalidates refresh tokens and cascades to child sessions, while revoking a child leaves its parent active. Deleting an instance or blueprint removes more resources and is irreversible. Already-issued access tokens may still pass local JWT verification until expiry--up to the configured TTL, which defaults to five minutes and is capped at one hour. For immediate cutoff, validate each token through WorkOS, trading a network call per request for checking that its backing session remains live. Revocation is idempotent; missing IDs return 404. Membership and sign-out changes can affect delegated sessions, but revocation does not undo data the agent already accessed or changed.

### Source excerpt

Agent sessions in WorkOS Agent Auth can be listed and revoked. Here is the removal routine, what a revoke stops, and how fast it takes effect in your API.

## One customer needs a role nobody else has: organization-scoped custom roles

DevFeed: [One customer needs a role nobody else has: organization-scoped custom roles](<https://devfeed.tech/articles/one-customer-needs-a-role-nobody-else-has-organization-scoped-custom-roles-115970.md>)

Original publisher: [Read original article](<https://workos.com/blog/organization-scoped-custom-roles>)

Author: WorkOS

Published: 2026-11-03T14:42:18Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [admin](<https://devfeed.tech/tags/admin.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [b2b](<https://devfeed.tech/tags/b2b.md>), [billing](<https://devfeed.tech/tags/billing.md>), [control](<https://devfeed.tech/tags/control.md>), [custom](<https://devfeed.tech/tags/custom.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [environment](<https://devfeed.tech/tags/environment.md>), [needs](<https://devfeed.tech/tags/needs.md>), [one](<https://devfeed.tech/tags/one.md>), [organization](<https://devfeed.tech/tags/organization.md>), [rest](<https://devfeed.tech/tags/rest.md>), [roles](<https://devfeed.tech/tags/roles.md>)

### AI overview

Organization-scoped custom roles let one WorkOS organization have customer-specific permissions without adding role options for every tenant. Create them on an organization's Roles tab or with POST /authorization/organizations/:organizationId/roles; new roles start without permissions, which must be set separately. Use a deliberate slug if application code depends on it: slugs cannot be changed, and custom slugs are unique within the organization. Creating the first custom role also forks that organization's default role and priority order from the environment's current settings; later environment changes no longer update those settings, so review them on the organization's Roles tab. A custom role cannot be deleted while it has active assignments or identity provider group mappings. Custom and environment roles appear together in the organization's role list and work with existing assignment paths.

### Source excerpt

Environment roles apply to every organization. A custom role belongs to one, so you can give a customer the role they asked for without touching the rest.

[Next page](<https://devfeed.tech/sources/workos-blog.md?cursor=WyIyMDI2LTExLTAzVDE0OjQyOjE4KzAwOjAwIiwgIjdiYTM2NjMwLTdiYTUtNDcyYS04NTc0LTI2MWMxMWJmM2YyYSJd>)