**Connected Apps** lists every third-party application *you personally* have authorized to act on your behalf in SendOps, across every organization you belong to. You can review what each one is allowed to do and disconnect any of them at any time.

Find it under **Profile → Connected Apps**.



This page is about **your own** authorizations. It needs no special permission — you are always allowed to see and revoke what you personally approved, whatever your role.


  **Connected Apps** (here, under your profile) is *apps you authorized*. **Workspace → OAuth Clients** is *clients your organization publishes for other people to connect to* — see [OAuth Clients](/api-integrations/oauth-clients). If you are looking for a client your team registered, you want that page instead.


## How an app gets here

When a product asks to connect to SendOps, you are shown a consent screen naming the app, listing the permissions it wants in plain language, and asking which of your organizations to grant. Approving creates the entry you see here.

You are shown that screen **every time** an app asks — including apps published by your own organization. There is no silent approval.

## What each entry tells you

- **Which app** — the name its developer registered.
- **Which organization** the grant applies to. Authorizing an app for one organization grants it nothing in the others.
- **What it can do** — the permissions you approved.

## What an app can actually do

Two limits apply at once, and both are checked on every single request:

- **What you approved** is the ceiling. An app can never exceed the permissions shown on the consent screen.
- **Your own role** is the floor. An app acting for you can never do something *you* could not do yourself.

The practical consequence is worth knowing: if your role is reduced later, every app you have connected quietly loses that access too. You do not need to revisit this page — it happens automatically.

## Disconnecting an app

Select **Disconnect** on any entry. This takes effect immediately: the app's tokens stop working and it cannot obtain new ones without asking you again.

Disconnecting affects **only your own** authorization. If a colleague has connected the same app for the same organization, their connection is untouched — each person's grant is theirs alone.


  Anything the app was doing on your behalf — a sync, a scheduled export — stops. If you want it back, you have to connect again from the app's own settings.


## When to disconnect

- You no longer use the product.
- You are leaving the organization, or changing role.
- You did not expect the connection, or do not recognize the app.


  Disconnect it, then tell your Owner or Org Admin. An organization admin can also review and revoke every grant across the organization from **Workspace → OAuth Clients**, which is the right place to check whether anyone else authorized the same thing.


## Organization-wide review

Admins are not limited to their own grants. From **Workspace → OAuth Clients**, an Owner or Org Admin can see every grant issued against the organization — whoever authorized it — and revoke any of them. That is the surface to use when off-boarding someone or auditing what has access.

Every grant and revocation is recorded in the [Audit Log](/team/audit-log).