📝 Everything you need to pass the Notion Advanced Quiz — explained like a friend who took good notes. 20 questions • Multiple choice • ~30 minutes • Pass and earn your Notion Advanced badge.

<aside>

Before You Take the Quiz

</aside>

<aside>

Quiz Information

Topics:

• Webhooks & integrations
• Workspace architecture (Home, OS, teamspaces)
• Databases, formulas & relations
• Wikis & knowledge management
• Notion AI & Enterprise Search
• Permissions at scale </aside>

<aside>

Quiz Information

Details:

• Format: 20 question, multiple-choice quiz
• Duration: About 30 minutes
• Recommended Prerequisites: Notion Advanced Learning Path
• Language: English

How it works:

1. Answer 20 multiple-choice questions.
2. If you pass, you'll be emailed a badge you can share! If you don't pass, fear not. You can always try again. </aside>

<aside>

Workspace design

• Teamspace — the default home for content mostly relevant to one team. Permissions inherit automatically — no manual setup required.
• Home — where company-wide, frequently-needed content lives so it's easy to find. Discoverability lives here, even when editing stays restricted underneath.
• Operating System (OS) layer — the shared structure (databases, templates, layouts) that teamspaces pull from, so every new team isn't reinventing their own setup from scratch.
• Page vs. database vs. wiki — a page is for content that rarely changes and just needs to display (a team landing page, an intro). A database is for anything that changes and needs tracking. A wiki is for the specific case of content that needs to be trusted and verified.
• Reusing existing structure — when a new team spins up, the fastest way to get them productive is pulling from what already exists — @-mention or sync in existing policies and templates — not starting from a blank page.

</aside>

<aside>

Database organization strategies

• Canonical database + linked views — the fix for teams drifting into their own scattered "Docs" databases. One shared source of truth, pulled into each teamspace via linked view — consistency without killing team autonomy.
• Relation — a property that links two databases together. One-way = visible from one side only. Two-way = navigable from either database.
• Rollup — pulls a calculated value from a related database (a count, sum, or latest entry). Requires the relation to exist first — a rollup has nothing to pull from without it.
• Verified wiki — the format for information that should be trusted by everyone and changes only occasionally, like a company policy. Verification + ownership is what makes it trustworthy at scale.
• Consolidate, don't duplicate — when new content overlaps with something that already exists, update and link the original rather than creating a second version. Duplication is how trust erodes.
• AI Connectors — extend Notion AI's reach into Slack and Google Drive, so it can synthesize answers from outside Notion too.
• Enterprise Search — ask AI a question and it pulls a cited, synthesized answer from across your entire workspace, respecting permissions.
• Enterprise Search filters — scope AI answers to a specific teamspace, date range, or doc type before you ask — keeps answers relevant as the workspace grows.
• What actually improves AI answer quality — verified pages with owners and review cadences, plus knowledge consolidated into wikis or canonical databases. Not more tags, not fewer connectors, not one giant unstructured database. </aside>

<aside>

Formulas

• Formula property — the property type for any value that needs to be calculated or derived from others — a RICE score, a due date offset, a generated ID. If it needs to compute, it's a formula, not a manual number field.
• dateAdd() — builds relative dates off another property, like setting a Due Date exactly two weeks after Start Date. Stays correct no matter when the task's created — unlike a static "2 weeks from now" default.
• Formula-generated IDs — a stable, machine-readable identifier (like ACCT-2025-08) built from other properties. Text can't derive from other fields — only Formula can.
• RICE scoring — prop("Reach") * prop("Impact") * prop("Confidence") / prop("Effort"). One formula property, no manual math, updates the moment any input changes. </aside>

<aside>

Webhook actions & integrations

• Webhook action — Notion sends data OUT to an external service when something happens in your database. Lives on a database automation. You control what triggers it and what it sends.
• Integration webhook subscription — an external service listens IN for changes, built at the integration level rather than one database — this is how you cover multiple workspaces at once.
• Scoped payloads — a webhook action should only include the properties the destination actually needs. Sending the full page is a security leak waiting to happen.
• Automation trigger + filter — the cleanest way to avoid noisy webhooks is to trigger on a specific property change (like Status) and filter for the exact transition you care about, not "any update."
• Page button vs. database automation — a button is for one-click, human-initiated chains. An automation is for anything that should fire on its own off a condition — no clicking required. </aside>

<aside>

Dictionary

</aside>

<aside>

‼️ Watch out

Two questions on this quiz sound nearly identical: one is about Notion sending data out (webhook action), the other is about an external service listening in for changes (integration webhook subscription). The direction of the data flow is the whole answer — get that backwards and you'll pick the wrong mechanism.

</aside>

<aside>

Lowkey Easy To Mix Up

• Webhook action vs. integration webhook subscription
• Button automation vs. database automation
• Wiki vs. canonical database with linked views </aside>

<aside>

What I actually need → Notion feature

• I want to send only certain info when something changes → Webhook action
• I want an outside tool to know the second something changes here → Integration webhook subscription
• I want a number that updates itself instead of me updating it → Formula property
• I want my due date to automatically follow my start date → dateAdd()
• I want a unique ID that builds itself from other info → Formula-generated ID
• I want live numbers from another database without copying anything → Relation + Rollup
• I want content only my team can mess with → Teamspace
• I want the important stuff easy to find for everyone → Home
• I want every new team to start from the same setup, not from scratch → OS + templates
• I want one page everyone can trust that doesn't turn into five versions → Wiki
• I want AI to also look through Slack and Drive → AI Connectors
• I want to ask one question and get an answer from my whole workspace → Enterprise Search
• I want AI to only look through certain pages → Enterprise Search filters </aside>

<aside>

</aside>

<aside>

</aside>

<aside>

</aside>