What Management OS does with your Notion workspace.

• Page and database contents within the pages you grant — when handlers need context (account plans, meeting notes, retro documents stored in Notion), they query designated databases inside the granted page set
• Search results within the granted page set — used on connect to find an existing "Management OS" page if one exists, and at runtime to locate context databases the workspace owner has configured
• Bot identity and Notion workspace name — returned by the OAuth token exchange so Settings can show which Notion workspace is connected

Notion enforces page-level access. We cannot read any page or database you did not explicitly grant during consent — and you can change the grant set later in Notion's integration settings.

Notion is one of the few places Management OS writes to, because it is where your briefs are delivered. The write surface is narrow and documented:

• Auto-provisioned parent page — on first connect, we look for a page titled "Management OS" in the granted page set. If one exists, we reuse it (idempotent on re-install). If not, we create it as a child of an accessible granted page, with a single explanatory paragraph as the landing content
• Auto-provisioned Brief Inbox database — created once, under the Management OS parent page, with our canonical schema: Title, Rule, Date, Severity, Status, Body. The structure is fixed so briefs are queryable from minute one
• New rows in the Brief Inbox database — every brief delivered via the Notion channel lands as a new page in the Brief Inbox database. The brief body is written as paragraph blocks under the row, with the deep-link back to Management OS as a final block

We do not modify or delete any page, database, or block outside the Management OS structure we created. We do not touch your existing Notion pages, your databases, your templates, or your workspace settings.

Notion's OAuth model is different from Google or Microsoft: there is no granular per-permission scope list. Instead, the user explicitly chooses which pages the integration can access during consent. Our access is limited to that set, enforced by Notion. The functional capabilities below document what Management OS actually does with the access granted — every action is gated by the user's page selection.

Application database: Supabase Postgres (Management OS's production database, US East). Encrypted at rest (AES-256), encrypted in transit (TLS 1.3). Workspace-scoped row-level security (RLS) means one customer's data is never visible to another.

OAuth tokens: The Notion access token (and associated bot ID, Notion workspace ID, Brief Inbox database ID) is stored in Supabase under workspace-scoped RLS, encrypted at rest, and never returned to client browsers. Notion access tokens do not expire automatically; revocation happens when the user removes the integration in Notion or disconnects in Management OS.

Inference layer: Anthropic API (Claude models). Notion content read for a specific brief or output is passed to Anthropic at inference time; outputs are returned to Management OS and stored in our database. Anthropic does not train on customer data per their API terms.

Retention: We retain Notion-sourced extracts while your subscription is active. On disconnect we delete the stored OAuth token immediately. The Brief Inbox database and the briefs already written into it remain in your Notion workspace — they belong to you. On subscription cancellation, customer data in Management OS is retained for 30 days for restoration, then permanently deleted. Data subject deletion requests are honored within 30 days per our Privacy Policy.

1. Sign up at mgmt-os.ai and complete onboarding to your workspace
2. Open Management OS → Settings → Integrations
3. Find Notion in the integration directory and click Connect Notion
4. You'll be redirected to Notion's OAuth consent screen. Sign in if needed, then choose which Notion workspace to install into
5. On the page-selection screen, grant the Management OS integration access to the page (or pages) you want it to be able to read from and write into. At minimum, pick a parent page where Management OS can create its own structure — a page titled "Operating Workspace," "Sales," or anything similar works. Click Allow access
6. On return, Management OS auto-provisions the Management OS parent page and the Management OS Brief Inbox database under it. Settings shows the deep-link to the new database so you can open it immediately

Notion lights up as a brief-delivery channel and as a context source:

• Brief delivery — when an automation rule fires, the brief lands as a new row in the Brief Inbox database. Three pillars route to the same database with the Rule and Severity properties distinguishing them: Develop Your Business (deal slips, champion shifts, renewal risk), Develop Your Team (coaching priorities, rep-effectiveness signals), Develop Yourself (calendar drift, decision deadlines)
• Context source — designated Notion databases (account plans, meeting notes, retro docs) that the workspace owner has configured become context for AI-generated outputs. Configured per workspace in Management OS settings
• Ask Anything (AMA) — you can reference Notion content in plain-English queries: "summarize what last week's retro says about pipeline coverage," "pull the account plan for Acme and tell me what stage we're in on the renewal."

1. Open Management OS → Settings → Integrations
2. Find Notion in the connected integrations list
3. Click Disconnect → confirm

On disconnect we delete the stored Notion access token immediately and stop reading or writing into Notion. The Brief Inbox database and the briefs already written into it remain in your Notion workspace — they belong to you. If you want them gone, delete the "Management OS" parent page in Notion (which deletes the Brief Inbox database and all rows under it).

To remove all historical briefs and Notion-sourced extracts from Management OS's side after disconnect, email privacy@mgmt-os.ai with your workspace identifier. We process deletion requests within 30 days.

1. Sign in to notion.so with the account that authorized Management OS
2. Open Settings & members → My connections (in the left sidebar of the settings dialog)
3. Find Management OS in the connected-apps list
4. Click the ··· menu next to it → Disconnect → confirm

Workspace admin path: a workspace owner can remove the integration for the whole Notion workspace from Settings & members → Connections → Management OS → Remove.

Revoking from Notion's side invalidates our access token immediately. Our next API call returns a 401 and we surface a re-connection prompt in Management OS Settings. The Brief Inbox database and existing rows are not deleted by revoke — those remain in your Notion workspace as historical content.

Security incident reporting: security@mgmt-os.ai
Privacy / data subject requests: privacy@mgmt-os.ai
Integration support: support@mgmt-os.ai

For general questions about Management OS, see our Support page or Manifesto.