Purpose

This page documents the intended permissions model for AI agents operating within the Next Effect Notion workspace, and provides the steps to enforce it.

Integration Details

Setting	Value
Integration Name	Notion MCP
Bot User ID	`24660266-75c5-81d0-a8e0-0027a206ed55`
MCP URL	`https://mcp.notion.com/mcp`
Workspace	Next Effect (teamspace ID: `30560266-75c5-812b-ae00-004243a9f781`)

Workspace Users

Name	Role	User ID
Kusa	Owner / CEO	`373ffe7d-6697-4d4d-9170-566b49276b7a`
Alex Barton	Team Member	`2c6d872b-594c-813d-9232-00021f9f26c4`
Notion MCP	Bot (Agent Integration)	`24660266-75c5-81d0-a8e0-0027a206ed55`

Intended Permissions Model

All OS Layer Databases — Full Read + Write Access

Database	Data Source ID	Operations
🎫 Tickets	`0669e4a6-6968-4665-9465-3f75ca22b5c0`	Create, read, update. Primary intake layer for all requests.
✅ Tasks	`30560266-75c5-81e3-8cda-000b5aadc7e8`	Create, read, update. Agents can spawn tasks from tickets.
📁 Active Engagements	`30560266-75c5-813a-8085-000b93c7aa32`	Read, update. Agents can link tickets and update engagement data.
🚀 Initiatives	`30560266-75c5-816a-954b-000be91a894f`	Read, update. Agents can link tickets and update initiative status.
🧩 Internal Projects	`30560266-75c5-81f1-8f52-000b5d903997`	Read, update. Agents can link work to internal projects.
Client Database	`30560266-75c5-8150-a92a-000bca7a5b85`	Read, update. Agents can reference client records and update notes.
Agent-generated child databases	(dynamic)	Create databases as children of ticket pages. Full read/write.
Page comments	(via page ID)	Create and read comments on any page across all databases.

How to Enforce

Notion's native integration permissions work at the page/database sharing level. The Notion MCP bot inherits access from what it's been shared with in the workspace. To enforce the model above:

Step 1: Verify MCP bot has workspace-level access

The Notion MCP integration should have workspace-level access to the Next Effect teamspace. This grants read/write to all databases listed above.

Step 2: Verify each database is accessible

For each OS Layer database, open Share settings and confirm the Notion MCP integration has "Can edit" access. Databases created through the MCP already have this.

Step 3: Convention-based guardrails

While all databases are technically accessible, the Agent Database Creation Convention and Agent Interface Spec define the expected workflow: tickets as intake → tasks as execution → child databases as work product. Agents should follow this flow even though they have broader access.