# Organizations support in OAuth Applications

OAuth Applications now integrate with Clerk Organizations. When your instance has Organizations enabled, users going through the OAuth flow can select which organization they're acting on behalf of, and the OAuth client receives that selection as an `org_id` claim on the access token.

![An OAuth Consent screen shows a dropdown selection expanded with 3 organizations to choose from](./image.png)

## How it works

We've added a new `user:org:read` scope to OAuth Applications. When a client requests this scope and the user grants it, the OAuth consent screen displays an organization selector. After consent, the access token issued to the client includes an `org_id` claim populated with the selected organization.

If the consent screen is disabled for your OAuth Application, `org_id` is populated with the user's last active organization instead.

For convenience, the userinfo endpoint also returns `org_name` and `org_slug` alongside `org_id`, so clients can display organization context without an extra lookup.

## Enabling it on an existing OAuth Application

Updating an existing OAuth Application is as simple as enabling the new `user:org:read` scope in its settings on the [Clerk Dashboard](https://dashboard.clerk.com/~/oauth-applications).
No other changes are required — once the scope is available, clients can request it on their next authorization request.

To learn more, see our [OAuth Applications documentation](https://clerk.com/docs/guides/configure/auth-strategies/oauth/how-clerk-implements-oauth.md#organizations-and-oauth).