Connecting Notion gives Indent your docs and wikis as a tool. Ask it to find a spec, summarize a meeting note, pull the runbook for an alert, or write results back to a page, and it works with Notion directly.
Connect Notion
Open the integrations page
Open Settings → Integrations and find Notion.
Choose a scope
Connect at organization scope to share the integration with your team, or personal scope to connect as yourself. A personal integration works only in a private session.
Authorize with Notion
Notion connects through its hosted MCP server. Sign in, choose the workspace, and select the pages and teamspaces to share. Indent can then use Notion in your sessions.
Use a service account for organization scope
A Notion service account is an ordinary workspace member that belongs to the team rather than to a person. Create one before you connect at organization scope.
Create an account on a shared address
Sign up for Notion with an address your team controls, such as a group alias like
indent@yourcompany.com. Keep the credentials in your password manager, not in one person’s
inbox.
Invite it to the workspace
From Settings → People in Notion, invite the address as a member. Give it the lowest role that still does the job — Member, not Workspace owner — so the integration can’t change workspace settings.
Grant only the content Indent should see
Add the service account to the teamspaces and share the pages you want Indent to work with. The integration can reach exactly what this account can reach, so this list is your access boundary.
Authorize Indent as that account
Sign in to Notion as the service account (a separate browser profile or incognito window avoids signing out of your own), then connect Notion at organization scope from Settings → Integrations and complete the OAuth flow.
Auditing and offboarding then work the way you’d expect: Notion attributes Indent’s edits to the service account, you widen or narrow the integration’s reach by changing that account’s page access, and revoking the connection is a single member to disable.
If you need a workspace-owned bot
Notion’s hosted MCP server accepts OAuth only — it won’t take an internal integration token — so a service account is as close to an application identity as the hosted server gets. When your policy requires a workspace-owned bot with no user session behind it, run Notion’s open-source MCP server yourself with an internal connection token and register it in Indent as a custom MCP server with API token authentication.
What Indent does with Notion
- Searches your workspace and reads pages and databases.
- Creates pages and writes results back into existing ones.
- Comments on pages.
- Queries databases and updates their entries.
Next steps
- Connecting MCP servers — the built-in MCP catalog and how scopes work.
- Permissions and data — what Indent can reach and how access is scoped.