Managing connected apps

Every app or assistant authorized over OAuth shows up on one screen — Connected apps, in your organization settings. From there you can see what each connection reaches, change which projects it covers, and disconnect it on the spot.

Where it lives

Connected apps is part of organization settings, not project settings: connections belong to the organization and can span several of its projects.

Anyone can open it and will see the connections they authorized themselves. If you have organization-level access, you get a second tab, Whole organization, with every connection in it and an extra User column showing who granted each one.

There is no "connect" or "create" button here, on purpose. Connections are always started from the outside — from the assistant or the app, which sends you to Instasent to approve it. This screen is where you review and manage the ones that already exist.

What the table tells you

Each row is one connection. The columns available are:

Column	What it tells you
App	The app's identity — its name, whether it is an MCP client or an API integration, and whether Instasent has verified it.
Permissions	How many permissions the connection holds. Hover the count to see the full list.
Projects	Which projects it reaches. A project shows a badge when its access type isn't Full access.
User	Who authorized it. Only in the organization-wide view.
Created	When it was authorized.
Last used	The last time the app actually used it.
Expires	When it lapses through inactivity, or Doesn't expire.

You won't necessarily see all of them at once: the table starts with the columns that answer the usual question and keeps the rest one click away in the column menu, and it remembers your choice for next time.

The same app can appear more than once

It's normal to see one app listed several times — one connection per project, or per device. Instasent doesn't merge them: each is independent, told apart by its projects and its dates, and disconnecting one doesn't touch the others.

Changing which projects a connection reaches

Edit projects changes which projects a connection can access without changing its permissions. That is how you widen or narrow its reach.

Adding new permissions is not something you can do from here: the app has to be authorized again from its side, so it can ask for the extra access and you can approve it.

Disconnecting

Disconnect cuts a connection's access. You confirm once, and the app loses access immediately — to come back it would have to be authorized from scratch.

When a connection lapses on its own

A connection expires through inactivity. The Expires column shows the date it would happen, or Doesn't expire. Every time the app uses the connection that date moves forward, so one in regular use never reaches it; one left alone for a long stretch lapses, and the app has to be authorized again.

This has nothing to do with the short-lived access the app uses behind the scenes for each request, which renews itself and needs nothing from you.

What's next

• Data access — how much of your data a connection actually receives, whatever it was granted.
• Connect your AI — how a connection gets created in the first place.