This set builds vocabulary for structuring and connecting data within a flexible workspace tool.
0 / 5 completed
1 / 5
At standup, a dev mentions a structured collection of pages, each with consistent properties like status and due date, viewable as a table, board, or calendar. What is this feature called?
A Notion database is a structured collection of pages sharing a consistent set of properties, like status or due date, that can be displayed in multiple formats, such as a table, kanban board, or calendar, all reflecting the same underlying structured data. This flexibility lets different team members view the same information in whichever format suits their workflow. It's a core building block for turning Notion from a simple document tool into a lightweight structured data platform.
2 / 5
During a design review, the team wants a property in one database to automatically pull in and display related records from a separate, connected database. Which capability supports this?
A relation property links records between two separate databases, so a record in one, like a project, can reference related records in another, like its associated tasks, keeping the connection live rather than requiring manually duplicated data. This mirrors a foreign-key relationship in a traditional relational database, applied within a more visual, flexible tool. It lets a team model genuinely interconnected information without flattening everything into a single, unwieldy database.
3 / 5
In a code review, a dev configures a formula property that automatically calculates the number of days remaining until a task's due date. What does this represent?
A computed formula property automatically calculates a derived value, like days remaining until a due date, based on other properties in the same record, updating live as those underlying values change rather than requiring manual recalculation. This brings spreadsheet-like computed logic into a structured database of pages. It's especially useful for surfacing at-a-glance derived insights without maintaining them by hand.
4 / 5
An incident report style retro shows a heavily nested set of relation properties across many databases made the workspace confusing and slow to navigate. What practice would address this?
Simplifying a database's structure and its relations to match what the team actually needs, rather than modeling every conceivable connection just because the tool supports it, keeps the workspace navigable and understandable. Over-modeling with excessive nested relations is a common way a flexible, powerful tool becomes confusing to actually use day-to-day. This restraint in structural design is a practical consideration for any team building out a complex Notion workspace.
5 / 5
During a PR review, a teammate asks why the team models related information as linked databases with relation properties instead of duplicating the data into each page manually. What is the reasoning?
Manually duplicating data across multiple pages risks the copies drifting out of sync whenever the original information changes, while a relation property keeps everything connected to a single source of truth that updates everywhere it's referenced. This consistency is the main advantage of modeling genuinely related information as linked databases rather than repeated, disconnected copies. The tradeoff is the added complexity of designing and maintaining the relational structure itself.