Get AI summaries of any video or article — Sign up free
Notion 3.0 Explained | Top Features & What's Coming Soon! thumbnail

Notion 3.0 Explained | Top Features & What's Coming Soon!

5 min read

Based on The Organized Notebook's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Granular database permissions enable row-level sharing so individuals can see and edit only the tasks that match specific rules like assignee and entry creator.

Briefing

Notion 3.0’s biggest practical upgrade is granular database permissions, letting workspace owners share only the rows and actions each person needs—without handing over the entire database. The example walks through a task tracker where a contractor, Sam, should see and edit only tasks assigned to them. Instead of granting full database access, the setup uses share rules tied to specific conditions (like the assignee and the entry creator). When Sam opens a shared page via a linked view, the database doesn’t even appear as a whole; it surfaces only the permitted task(s), and Sam can edit within those boundaries.

That row-level control comes with a key limitation: permissions can’t be restricted down to individual properties. If a status field is editable, Sam may still change it in a way that effectively removes the task from their view—because the filtering logic depends on the assignee/status relationship. The transcript also highlights a cleaner use case: making the assignee property view-only at the page level. In that scenario, Sam can view the shared tasks but can’t alter fields that would change what they see, making the permissions model more predictable for internal sharing.

The other major pillar of Notion 3.0 is Notion Agent, positioned as a more personalized AI layer that can follow custom instructions and take actions inside a workspace. Users can personalize Notion AI with guidance text and even “instructions” that shape tone and behavior. The agent can create new pages—such as generating a new project—then clearly indicates where it placed the content and allows undo if the result isn’t wanted. It can also apply templates, including a workflow where a user provides a transcript or images and the agent generates content (like captions), with options to store drafts in a database.

On the automation side, Notion AI formulas add a no-formula-writing path: users can add a formula property and ask AI to write, fix, or explain the formula in plain language. The example demonstrates conditional logic for task trackers—marking overdue tasks with an “overdue” tag, hiding the formula output when tasks are done, and applying styling rules like bold and green text based on status.

Notion is also expanding AI connectors so chat-based assistance can pull in context beyond Notion pages—specifically including Notion Mail—then use that combined information to compile reports. Looking ahead from Make with Notion, two features are flagged as coming soon: a team of custom agents that can operate with roles, triggers, and cycles (for example, generating weekly reports or reacting to Slack messages), and a Maps view database for storing locations and visualizing them on a map—useful for travel planning or restaurant lists.

Taken together, the updates shift Notion from a static workspace into a more controlled collaboration environment and a more action-oriented AI system—where access rules, content generation, and workflow automation can be tailored to specific people and recurring needs.

Cornell Notes

Notion 3.0 adds granular database permissions, enabling row-level sharing so individuals can see and edit only the tasks meant for them—without exposing the entire database. The setup uses share rules tied to conditions such as assignee and entry creator, and linked views show only permitted rows. A notable constraint is that permissions can’t be limited to individual properties, so editable fields like status can affect what appears in a filtered view. Notion Agent brings personalized, instruction-driven AI that can create pages, apply templates, and store generated drafts in databases. Additional upgrades include AI-assisted formulas, more AI connectors (including Notion Mail), and upcoming features like custom agent teams and Maps view databases.

How do granular database permissions work in practice, and what problem do they solve?

The permissions model lets a workspace owner share a database without granting full access. In the example, Sam should only see tasks assigned to them and be able to edit those tasks. Instead of sharing the database broadly, the owner sets share rules in the database’s share settings—adding conditions such as “assignee can edit” and “entry creator can edit.” When Sam opens a shared page that contains a linked view of the database, the database doesn’t appear as a full dataset; Sam sees only the permitted task(s) and can edit within those allowed rules.

What limitation comes with granular permissions, and why does it matter?

Notion can’t restrict access down to specific properties. If a field like “status” is editable, Sam can still change it. Because the view is filtered based on task attributes, changing status (or related logic) can cause the task to disappear from Sam’s page. The transcript frames this as a configuration challenge and suggests that deeper investigation may be needed.

Why is making the assignee property view-only a recommended use case?

The transcript suggests a safer pattern: keep the assignee property view-only at the page level. In that setup, Sam can view the shared tasks but can’t edit the fields that would alter which tasks qualify for their view. That makes the permissions behavior more predictable for people who need read access plus limited editing elsewhere.

What can Notion Agent do beyond answering questions?

Notion Agent can take actions in the workspace. Users can personalize it with instructions (including tone preferences) and then ask it to create new pages—such as generating a new project—after which the workspace shows where the page was placed. It also supports undo if the generated page isn’t desired. The agent can apply templates and generate content from inputs like transcripts or attached images, and it can populate a database with stored drafts.

How do AI formulas reduce friction for building conditional logic?

AI formulas let users add a formula property and ask AI to write, fix, or explain the formula in natural language. The example shows a task tracker where overdue tasks display an “overdue” tag, while tasks marked “done” don’t show the overdue output. The same approach extends to styling rules—like making text bold and green when a condition is met—without requiring the user to manually craft the formula syntax.

What’s coming soon that expands automation and visualization?

Two upcoming features are highlighted. First, a team of custom agents that can act in roles and run on triggers and cycles—such as producing weekly reports or responding when someone sends a Slack message. Second, a Maps view database that stores locations and displays them on a map, enabling use cases like travel planners and restaurant lists.

Review Questions

  1. In the granular permissions example, which share rules determine what Sam can see and edit, and how does the linked view affect what appears?
  2. Why can editable properties like “status” undermine the intended permissions behavior, and what workaround does the transcript suggest?
  3. Describe two distinct ways Notion 3.0 uses AI to create value: one for content generation or page creation, and one for formulas or connectors.

Key Points

  1. 1

    Granular database permissions enable row-level sharing so individuals can see and edit only the tasks that match specific rules like assignee and entry creator.

  2. 2

    Linked views on shared pages can hide the database as a whole while still showing only permitted rows to each person.

  3. 3

    Permissions can’t be limited to individual properties, so editable fields (e.g., status) may let users change data in ways that alter filtered views.

  4. 4

    Notion Agent supports personalization via instructions, can create new pages (like projects), and can undo actions if results aren’t wanted.

  5. 5

    AI formulas let users generate conditional logic and styling rules by asking AI to write, fix, or explain formulas in plain language.

  6. 6

    AI connectors expand context beyond Notion pages, including Notion Mail, improving report compilation and chat-based assistance.

  7. 7

    Upcoming features include team-based custom agents with triggers/cycles and a Maps view database for location-based planning.

Highlights

Granular permissions can make a database effectively “disappear” for a collaborator while still showing only the rows they’re allowed to access via a linked view.
Notion Agent can generate workspace pages on demand and clearly indicates where content was created, with an undo option.
AI formulas support conditional outputs and styling (like overdue tags and bold/green text) through natural-language prompts.
Upcoming custom agent teams aim to automate recurring work with triggers and cycles, including Slack-driven events.
Maps view databases promise a straightforward way to store locations and visualize them directly in Notion.

Topics

  • Granular Permissions
  • Notion Agent
  • AI Formulas
  • AI Connectors
  • Maps View Databases