# Consent screens

OhAuthCat shows two kinds of consent screen.

## SSO sign-in consent

After an enterprise SSO sign-in, the broker can show a short screen naming your app and the organization before returning to your app. It is **on by default** for every environment and can be turned off per environment by setting `consent_screen_default` to `off` with `PATCH /v1/environment`. Declining answers [`consent_declined`](/errors/consent_declined/).

The screen uses your [branding](/hosted-portal/branding/): from Pro, the organization's logo and color and a separate consent branding set, including a favicon and a custom font served from the OhAuthCat assets origin.

## Connected-app consent

For the [OAuth provider](/oauth-provider/), first-party clients never ask. Third-party clients ask the user to approve the requested scopes and resource, unless a live grant already covers them or the client sends `prompt=consent`. Approving creates or widens the grant. Each scope's text comes from `PUT /v1/oauth/scopes/{scope}`, and the client's name, logo and `consent_text` from its registration. Dynamic clients registered by [MCP clients and agents](/oauth-provider/mcp/) always ask.
