Admin controls for integrations
The switches Owners and Admins have over integrations: who manages them, personal tokens, AI assistants, the app allowlist, connected apps, the audit trail and a full workspace export.
Most of these live in Org Settings → Integrations. On a phone you can see what's set up and disconnect things; changing settings is done on a computer.
Who may manage integrations
The Manage integrations permission lets someone set up and change every integration in the org: webhooks, event subscriptions, apps and bots, feeds, bridges, the native connections and the rest.
| Who | Has it |
|---|---|
| Owners and Admins | Always. A custom role can't take it away. |
| Members | Only through a custom role that grants it. |
| Guests | Never. |
To give it to someone, open Org Settings → Roles, pick or make a custom role, and under Organization turn on Manage integrations. If a member holds several custom roles that say different things, the highest role in the list decides, as with channel permissions.
A few settings below are for Owners and Admins only, even if a custom role grants Manage integrations: personal tokens, AI assistants, who may connect apps, and the app allowlist. Someone with only the permission sees these settings but can't change them.
Some integrations can also be managed per channel by the channel's managers, such as a channel's email address and adding an app to a channel.
Personal tokens
By default, any member can make a personal API token that reaches your org, limited to their own permissions. An Owner or Admin can keep personal tokens to Owners and Admins: Org Settings → Integrations → API tokens, then Owners and admins only. The section then reads "Only owners and admins may use personal API tokens here."
While it's off, Members' and Guests' tokens stop reaching your org at once. They aren't revoked: they keep working in the person's other orgs, and they reach yours again if you choose Allow members' tokens. App tokens are not affected. See Authentication.
AI assistants (MCP)
Org Settings → Integrations → AI assistants (MCP) decides whether members can connect Claude, Cursor and other assistants to your org through the MCP server. An assistant acts as the member who connected it and sees only what they can.
- The default depends on the plan: on for Free, Ministry and Creator orgs, off for Business orgs.
- An Owner or Admin can Turn on or Turn off, and later Use the default to follow the plan again.
- Turning it off cuts every member's assistant off at once, whether it signed in or uses a personal token.
Every tool an assistant uses is in the audit log (which tool, whether it wrote, the outcome), never what it read or wrote.
Apps from the gallery
Anyone with Manage integrations can add apps from Org Settings → Integrations → Browse apps. Each app's page shows its maker, what it may do and why. See App gallery.
The app allowlist
Available on the Business plan. A self-hosted server has every feature on.
Under Browse apps → App allowlist, an Owner or Admin can Turn on the allowlist. While it's on, only the apps on your org's list, and apps made in your org, can be added or connected, by bots or by members signing in. Apps already installed when you turn it on are put on the list for you.
On an app's page, choose Allow in this org or Remove from this org's list. The list is checked whenever an app is added or someone connects it; to stop an app that's already installed, pause or uninstall it.
Pausing and uninstalling apps
Each installed app has a card under Org Settings → Integrations → Apps & bots:
| Button | Does |
|---|---|
| Pause / Resume | Its tokens, slash commands, buttons and gateway connection stop working until you resume it. Nothing is revoked. |
| Change scopes | Every token of the app takes the new scopes at once. |
| Remove from a channel | The app stops seeing that channel. |
| Uninstall | Its tokens stop working, it leaves every channel, and the event subscriptions its tokens made are deleted. Its past messages stay. |
An app's token can also be revoked on its own from the same card. See Apps and bots.
If the platform suspends an app for breaking the rules, its installs are paused in every org. That pause lifts only when the platform lifts the suspension; a pause you set yourself stays until you resume it.
Connected apps
Org Settings → Integrations → Connected apps lists everything connected to your org through OAuth:
- bot: an app someone added with "Add to Missived".
- signed in: a member who used "Sign in with Missived" with an app, acting as themselves.
- AI assistant: a member's assistant that signed in, acting as them.
Each row says who added it, when, and what it Can do. Remove (for a bot) or Disconnect ends it at once.
Members may connect apps sets what members can connect for themselves. Owners and Admins can always connect apps to their own account; adding a bot always needs Manage integrations.
| Setting | Members can |
|---|---|
| Off | Connect nothing. Only Owners and Admins can connect apps to their account here. |
| Sign-in only (the default) | Use "Sign in with Missived": an app learns who they are and which orgs they're in, nothing more. |
| Sign in and act as them | Also let an app read and post as them, within the scopes they approve. Never direct messages, never admin scopes. |
Only an Owner or Admin can change the setting.
The audit trail
Every change to an integration is recorded in the org's audit log (Org Settings → Audit log), with who did it, when and from where. See Audit logs to read it or stream it to your own server.
What gets recorded, in plain words:
- Integrations: each integration made, changed, paused, resumed, deleted or paused automatically (webhooks and their secrets, event subscriptions, feeds, bridges and their links, email addresses, GitHub, the streaming and supporter connections, game servers, Planning Center, Bible verses); the AI assistants switch; the personal-token setting; replayed deliveries.
- Apps: an app made, changed or deleted; installed or uninstalled; paused or resumed; its scopes changed; added to or removed from a channel.
- Tokens: a token made, revoked or expired, its first use, and use from a new address.
- Connected apps and the gallery: consent given or refused, a connection revoked, the members setting changed, the allowlist turned on or off, an app allowed or removed.
- AI assistants: each tool call, with the tool and outcome.
The audit log never holds secrets, tokens, webhook URLs, link codes, or message content.
Export the workspace
An Owner can download a copy of everything the workspace holds: Org Settings → Data → Export this workspace… (Admins don't see the Data tab).
- Choose whether to Include files. Unticked, the copy has the messages and a list of files, without the files themselves.
- Enter your password, and the code from your authenticator app if you use one.
- Choose Prepare the export. You get an email and an Activity item when it's ready, then Download.
The other Owners and the Admins are told when an export is asked for, and every request and download is in the audit log. A workspace can be exported once a day. The copy is deleted 7 days after it's ready, or sooner with Delete now; a download link works for 10 minutes.
What's in it: a zip that opens offline (start with index.html), with JSON for everything:
- the workspace's settings, members (names, emails, roles, departments), custom roles, categories and channels with their permission overrides;
- every message in every channel, private channels included, with threads, reactions, pins, app cards and files;
- Knowledge pages, whiteboards, Tables (as CSV and Excel values), polls, prayer requests (anonymous ones stay anonymous), flash cards, task boards, meetings, shifts, events, meal trains, the audio library and custom emoji;
- the audit log.
In an org that encrypts content, the copy is decrypted.
Never in it:
- Direct messages, group chats and personal channels. They belong to the people in them; each person can download their own copy from Settings → Account → Download my data.
- Passwords, two-factor secrets, sign-in sessions, API tokens, webhook and integration keys, meeting passcodes and manage links.
- Each person's own settings, read state, saved messages and study progress, and any other workspace's data.