Your workspace,
answered from chat.
Ask Other Me to find a page, summarise a database, draft meeting notes, or log an entry — without leaving the chat window. Notion stays the source of truth; the assistant only sees the pages and databases you explicitly share with it.
Stop hunting for that page
Ask. Notion answers. The assistant writes back for you.
You
“Find my sprint notes from last Tuesday and summarise the action items.”
Other Me
Found “Sprint 24 — Apr 15”. Three action items: ship Stripe webhook retries (Alex, Fri), polish signup error copy (Nia, Thu), investigate S3 403s (you, Wed).
You
“In my CRM database, which contacts are marked Hot and haven’t been touched in 30 days?”
Other Me
Seven rows match. Top three: Acme Ltd (last contact 42 days ago), Beta Co (38), Delta Inc (33). Want me to draft follow-up notes for each?
You
“Create a page called ‘Q2 roadmap’ under my Strategy hub and add three sections: Now, Next, Later.”
Other Me
📝 Created “Q2 roadmap” under Strategy hub with three H2 sections.
You
“Mark the onboarding task as Done.”
Other Me
✅ Updated Status on the Onboarding page to “Done”.
What the assistant can do
Seven tools, every one SCRS-gated under the Docs scope.
Two consent layers, one audit trail
Notion’s per-page consent + SCRS scope — defence in depth.
Layer 1 — Notion consent
On the Notion consent screen you explicitly pick which pages and databases the integration can see. Other Me cannot discover anything you didn’t share — this is Notion’s security model, and we run within it.
Layer 2 — SCRS Docs scope
An organisation admin can disable the Docs collection for the whole tenant. When disabled, every Notion tool blocks at call time with a clear message, regardless of what individual users shared.
Gate 2 — DLP on writes
On create / update / append, the LLM-synthesised page content is scanned for PII and secrets before it leaves your server. Block-only — redacting a customer name in a page body would silently corrupt the note.
Audit ledger
Every call writes a hash-chained row to SCRSAuditLog with gate=tool. Same SIEM drain as the rest of SCRS.
Three minutes to connect
-
1
Settings → Integrations → Connect Notion.
-
2
Pick your workspace on the Notion consent screen.
-
3
Choose exactly which pages and databases you want Other Me to see. You can share more any time by opening a page in Notion → “+” → “Add connections” → “Other Me”.
-
4
Back in chat. Every call is scope-gated, DLP-scanned on writes, and audit-logged.
What’s deliberately not in v1
Four constraints. Here’s why.
Limited block types for writes
Paragraph, heading (H1–H3), bulleted list, and to-do. Tables, columns, embeds, synced blocks, and databases-inside-pages aren’t supported for writes yet. Reads flatten any block type to text.
Limited database property types for writes
Title, rich text, number, select, status, date, checkbox, URL, email, phone. Formula, rollup, relation, people, and files are READ-ONLY — write attempts return a clear “not writable in v1” error instead of silently dropping the value.
Poll-based, not push
Notion does have webhooks, but public integrations need separate approval. v1 is on-demand queries only. Ask “what changed today?” and the assistant will check.
One workspace per connection
Each Notion connection is scoped to one workspace. If you work across multiple workspaces, connect the one you use most; switching later is a disconnect-and-reconnect on the Settings page.
Stop tab-hopping. Start asking.
Connect Notion, keep your governance. Free on every plan.
Try it free