How to Manage Notion Workspace Bot Integrations From Settings Panel

You need to control which bots and automated services can read or write data inside your Notion workspace. Bot integrations include Slack bots, Zapier connections, GitHub automation, and custom API tokens. This article explains how to view, add, and remove these integrations from the workspace settings panel.

Notion uses a permission system where each bot operates under a specific connection. Without proper management, a bot can access more data than intended or stop working after a token change. You will learn the exact steps to review all active bots, revoke access for outdated ones, and add new integrations safely.

By the end, you will know how to audit your workspace’s external connections and prevent unauthorized data access. This guide covers the settings panel for both free and paid Notion plans.

How Bot Integrations Work in a Notion Workspace

A bot integration is a third-party service that connects to Notion using an API token. Each token belongs to a specific integration registered under a Notion account. When you grant access, the bot can read, create, or update pages and databases that you explicitly share with it.

Workspace admins control which integrations exist in the workspace. The settings panel shows all integrations that have been authorized by any member. You cannot see integrations created by another workspace unless they have been shared with specific pages.

The permission scope of a bot is set when the integration is created. Scopes include read content, insert content, and update content. A bot cannot access pages or databases that have not been shared with it, even if the token has full scope. This two-layer permission model protects your data from overreaching automation.

Every integration appears in the workspace settings regardless of who created it. This gives admins a central view of all external connections. You can disconnect any integration from this panel, which immediately revokes the bot’s token.

Steps to View and Manage Workspace Bot Integrations

Follow these steps to access the integration management panel and perform common actions.

1. Open Workspace Settings
   Click the workspace name in the top-left corner of the Notion sidebar. Select Settings & Members from the dropdown menu. The settings panel opens by default on the General tab.
2. Navigate to Integrations
   In the left sidebar of the settings panel, click Integrations. This section contains two subsections: Workspace Integrations and Internal Integrations. Click Workspace Integrations to see all bots authorized by any workspace member.
3. Review the List of Active Bots
   The list shows each integration’s name, the Notion user who authorized it, and the date it was added. Hover over any row to see the integration’s ID and a brief description. Use this list to identify bots you no longer recognize or use.
4. Disconnect a Bot
   Click the three-dot menu (⋮) on the right side of the integration row. Choose Disconnect. A confirmation dialog appears. Click Disconnect again to confirm. The bot’s token is revoked immediately. The bot can no longer access any shared pages or databases.
5. Add a New Integration
   Click the Add Integration button at the top of the Workspace Integrations list. A dropdown shows two options: Connect a service and Create a custom integration. Select one based on your need. For a prebuilt service like Slack or Zapier, choose Connect a service and follow the authorization flow. For a custom bot, choose Create a custom integration and name it. Notion generates an API token. Copy the token immediately because you cannot see it again.
6. Share a Database or Page With a Bot
   Open the database or page you want the bot to access. Click the Share button in the top-right corner. In the Invite field, start typing the integration’s name. Select it from the dropdown. Choose the permission level: Can Read, Can Edit, or Can Comment. Click Invite. The bot now has access to that content only.
7. Edit an Integration’s Name or Description
   Click the integration name in the Workspace Integrations list. The integration detail page opens. You can change the name and description. Changes apply to all tokens and connections for that integration. Click Save.

Common Issues When Managing Workspace Bot Integrations

A bot shows as active but no longer works

The bot’s token may have been revoked or the integration may have been deleted by its creator. Check the Workspace Integrations list. If the bot appears but has no recent activity, disconnect it and ask the bot owner to create a new integration. If the bot does not appear, it was likely an internal integration that was deleted.

Cannot see the Add Integration button

Only workspace owners and admins can add integrations. If you are a member, the button is hidden. Ask an admin to add the integration or upgrade your role temporarily. You can check your role under Settings & Members > People.

Integration list shows duplicates of the same bot

Each authorization by a different workspace member creates a separate entry. For example, if two people connected the same Slack workspace, you see two entries. You can safely disconnect one if the bot works with only one connection. Confirm with both users before removing any entry.

Bot still has access after disconnecting

Disconnecting from workspace settings revokes the token. However, if the bot was shared with a page using a different method, such as a public link, it may still read that page. Remove the bot from the page’s Share menu as a secondary step.

Workspace Bot Integration Types Compared

Feature	Workspace Integration	Internal Integration
Who can create	Workspace admins and owners	Any workspace member
Visible in settings	Yes, under Workspace Integrations	Yes, under Internal Integrations
Token scope	Set by integration creator at creation	Set by integration creator at creation
Can be shared with pages	Yes	Yes
Can be disconnected by admins	Yes	Only by the creator or an owner
Use case	Prebuilt services like Slack, Zapier, GitHub	Custom scripts or private bots

Both types appear in the Integrations section of workspace settings. The main difference is who can disconnect them. Workspace integrations can be removed by any admin, while internal integrations require the creator or an owner to revoke.

Use workspace integrations for team-wide automation. Use internal integrations for personal experiments or one-off automations that should not be visible to the whole workspace.

To change an internal integration to a workspace integration, you must create a new integration under the workspace admin account and share the same pages.

Best Practices for Securing Bot Integrations

Audit your workspace integrations monthly. Remove any bot that you do not recognize or that has not been used in 90 days. A disconnected bot cannot be reconnected without a new token, so keep a record of which services each bot supports.

Use the minimum permission scope when creating a custom integration. For example, if a bot only reads data, select read-only scope. Do not grant update or insert permissions unless the automation requires them. You cannot change the scope after creation, so create a new integration with the correct scope if needed.

Store API tokens in a password manager or environment variable. Never paste a token into a shared document or chat. If a token is exposed, disconnect the integration immediately and create a new one.

For sensitive workspaces, restrict who can create internal integrations. Notion does not have a built-in toggle for this. Instead, train your team to request integrations through an admin rather than creating them directly.

You can now manage every bot integration from the workspace settings panel. Review the Workspace Integrations list monthly and remove any connection that is no longer needed. For custom automation, create internal integrations with the least privilege scope required. Use the keyboard shortcut Ctrl + / to quickly open the settings search bar and jump directly to Integrations.