Notion setup

You're reading the new setupAlready have Notion connected? →

Connecting Notion takes one guided setup. It authorizes Notion's MCP server and collects your indexing credentials, so it gives you two things.

• Read and write tools work right away, as soon as you authorize the MCP connection. Glean and Glean agents can search Notion, fetch pages and comments, and create or update pages, databases, and comments. Every tool runs as the person asking, using their own Notion authorization, so it respects that user's Notion permissions.
• Org-wide search is part of the same setup. You provide the indexing credentials during setup, and Glean builds a search index from the pages, databases, and blocks you share with it. This index is not permission-aware, so any shared content is visible to every Glean user who can access the connector.

Feature availability after setup

Read and write tools work as soon as you authorize the MCP connection. Indexing is part of the same setup, so org-wide search switches on automatically once the first crawl completes.

Capability	When it becomes available	Whose permissions apply
Read and write tools	After you authorize the connection	Each user's own Notion permissions, through their own Notion authorization
Org-wide indexed search	Once the first crawl completes	None at the document level. All content shared with the integration is visible to every Glean user who can access the connector.

Because the indexed corpus is not permission-aware, share only content that is appropriate for org-wide visibility. The tools stay scoped to each user's own Notion permissions on every call.

Prerequisites

Confirm the following before you begin.

Requirement	Why it is needed
A Glean admin who can add and configure connectors	Adds the Notion connector and completes setup in the Admin console
A Notion workspace admin	Authorizes Notion's MCP server, creates the Glean integration, and shares the pages and databases to index

Step 1. Connect and authorize

Sign in to Glean and go to Connectors in the Admin console. Add the Notion connector and enter a display Name for it. This is the name your organization members see.

Use individual authorization unless your organization has configured Cross App Access (XAA) with Okta. Both methods authorize tools for each user and respect that user's Notion permissions. Neither changes indexing credentials or indexed-content visibility.

Connect each user's account

With individual authorization, each teammate connects their own Notion account before using tools:

1. If the User authorization setting appears, keep Each user connects their own account selected.
2. Click Connect. Glean redirects you to Notion to authorize the connection. Grant the requested permissions.
3. After you connect, the setup flow advances automatically to the next step.

Completing this step enables read and write tools for your account. Teammates authorize their own accounts when they first use a Notion tool. See Manage tools for how to change which tools are on, where they appear, and who can use them.

Set up Cross App Access

Cross App Access is an alternative for eligible Notion MCP connections. Okta authorizes access on behalf of each user, so users don't need to connect Notion separately.

Prerequisites for Cross App Access

Before choosing this option:

• Your Notion workspace must use the Enterprise plan.
• Notion SAML single sign-on must use the same Okta organization that users use to sign in to Glean.
• You need an Okta admin and a Notion organization owner. If you don't use Notion organizations, you need a workspace owner.
• Notion must enable enterprise-managed connections for Glean. Contact Notion if Glean isn't available as a supported AI app.
• Each user's Okta identity must match their Notion member identity.

Complete workspace-level Cross App Access setup in Glean and Okta, including the Glean AI agent and token exchange endpoint. Allow Notion to use Cross App Access in your Glean workspace. If the option isn't available, contact your Glean representative to confirm eligibility and setup requirements.

For vendor requirements, see Set up enterprise-managed connections for Notion MCP.

Configure Glean, Okta, and Notion

Register the Notion OAuth client in Glean first, then use its client ID to complete the Okta and Notion configuration:

1

Register Glean's Notion OAuth client

1. Select Cross App Access in Glean.
2. Click Register OAuth client. Glean registers an OAuth client with Notion and displays its client ID.
3. Keep the Glean setup page open while you finish the Okta and Notion configuration.

This Notion client ID is not the Glean AI agent's workspace-level client ID. You don't need to enter a Notion resource client ID or client secret in Glean.

2

Configure the Notion application as a resource server

1. In the Okta Admin Console, go to Applications → Applications and open your Notion application.
2. Select the Resource server tab.
3. Enable Cross App Access and set the Issuer URL to https://mcp.notion.com.
4. Save the XAA configuration.

3

Add the resource connection to the Glean AI agent

1. In Okta, go to Directory → AI Agents and open the AI agent linked to your Glean sign-on application.
2. In Resource connections, add your Notion application.
3. Configure:
   • Resource indicator: https://mcp.notion.com
   • AI agent's client ID registered in this app: the Client ID displayed in Glean.
4. Allow the Notion MCP scopes required by your organization.
5. Save the resource connection and activate the AI agent.

Use https://mcp.notion.com for the Notion issuer and resource indicator, not the MCP transport URL https://mcp.notion.com/mcp or your Okta organization's issuer URL.

4

Enable the connection in Notion

1. In Notion, go to Settings → Identity → Enterprise-managed connections. If a Notion organization manages SAML, open its organization console.
2. Turn on enterprise-managed connections.
3. Confirm that the Okta issuer matches the Okta organization that provides Notion SAML single sign-on.
4. Select the workspace for this connection, then click Turn on.
5. Go to Settings → Connections → Permissions.
6. Under AI apps, approve Glean. Your existing Notion MCP allowlist still applies.

Return to Glean and click Finish setup. Ask users to sign out of Glean and sign in again before they use the Notion MCP tools.

Continue to set up indexing. Cross App Access does not replace the internal integration token or change which indexed content is visible to other users.

Step 2. Set up indexing

Provide the credentials Glean needs to index your Notion workspace.

1. Create the Glean integration in Notion at Notion my-integrations, associate it with your workspace, give it read capabilities, and copy its internal integration token.
2. In The name of your workspace, enter your Notion workspace name. Paste the token into Integration Token.
3. Share the pages and databases you want indexed with the Glean integration. Child pages of a shared page are shared automatically.
4. Select Continue to advance to the next step.

Share only content that is appropriate for org-wide visibility, because the indexed corpus is visible to everyone who can access the connector.

Step 3. Review setup

Review your setup, then select Begin indexing. Glean runs the initial crawl in the background. By default, Glean schedules a full crawl every six hours to keep content fresh. Finishing this step returns you to the connector's Overview page.

Manage tools

Authorizing the MCP connection makes Notion's tools available. You can see all available tools on the Tools tab of your connector and edit permissions through Advanced settings.

Tool settings you can change afterwards

• Which tools are on. Keep read tools enabled and leave write tools off until you are ready for agents to act in Notion. See Enabling or disabling individual tools.
• Where they appear. Across Glean Assistant, Agents, and the Glean MCP server. See Enabling tools for Chat and Agents.
• Who can use them. Scope each tool to specific users or groups. See Tool visibility scoping and role-based access to tools.
• How write tools run. Control whether a tool runs without user confirmation. See Run tools without user confirmation and Allowing in-line execution of write tools.

For the full guide, see Tools overview.

Per-user authorization

Setup authorizes Glean to Notion at the connector level and allows user-specific capabilities:

Capability	Runs as	What it enforces
Read and write tools	Each user's own Notion account	That user's own Notion permissions, checked by Notion on every call
Indexed search	The Glean integration	No per-user permissions. All content shared with the integration is visible to every Glean user who can access the connector.

With individual authorization, each teammate connects their own Notion account over OAuth the first time they use a tool. Until they do, Glean answers their Notion questions from indexed content only.

If your admin has configured Cross App Access for this connection, Okta authorizes on behalf of each user without a separate Notion consent flow. Tools still run with that user's Notion permissions. Cross App Access uses OAuth token exchange and does not grant organization-wide access to private content. See Set up Cross App Access.

If you connected your Notion account individually, you can disconnect and reconnect your personal authorization for the native Notion connector's Live Mode without changing the indexing integration. See Disconnect your Notion account.

For standalone Notion MCP connections, see Disconnect Notion MCP.

After setup

• Broaden coverage by sharing more pages and databases with the integration.
• Segment content by team by configuring multiple Notion connector instances, sharing a different subset with each, and restricting each connector's visibility to the right teammates. This separates content at the group level. The tools stay per-user permission-aware on their own.
• Check progress any time from the Notion connector page in the Admin console.

See also

• Choose your Notion setup shows which setup is yours and how tools and indexed search fit into each.
• Notion overview covers objects, crawling, permissions, and limitations.
• Connect Notion with Glean is the existing connector setup reference.