Notion Certification key terms

The top-level container that holds all pages, databases, members, and settings for an organization or team in Notion. Permissions, billing, and security controls apply at this level.

A person invited into a workspace with a login tied to an email address. Members can be assigned workspace-level roles and granted access to specific pages or databases.

A person granted access to a limited set of pages without full workspace membership. Guests see only what is explicitly shared and cannot browse the wider workspace.

The highest workspace role, able to manage billing, security settings, member roles, and workspace-wide configuration. Owners can also delete the workspace and transfer ownership.

A workspace role that can manage members, groups, and settings but typically lacks billing control. Admins help run day-to-day administration without full owner privileges.

A named collection of workspace members used to grant page or database access in bulk. Groups simplify permission management and can be referenced when sharing content.

The access tier assigned to a person or group on a page or database, such as full access, edit, comment, or view. Levels determine what actions a user can perform on that content.

Access control applied to an individual page or database rather than the whole workspace. It can be inherited by child pages or restricted to specific people and groups.

The behavior where child pages and nested content receive the permissions of their parent page automatically. Breaking inheritance allows a page to have its own separate access list.

The interface used to invite people, groups, or guests to a page or database and set their permission level. It also controls link sharing and copying a public link.

A setting that makes a page viewable by anyone with its URL, optionally allowing editing or duplication. Administrators can restrict or disable this capability workspace-wide.

An identity standard used to automatically create, update, and deactivate workspace members from an identity provider. It reduces manual member management and speeds offboarding.

A single sign-on protocol that lets members authenticate through an external identity provider instead of separate Notion credentials. It centralizes login control and supports enforced authentication policies.

An external service that manages user identities and authenticates them, such as Okta or Microsoft Entra ID. It connects to Notion through SSO and provisioning integrations.

An extra login verification step beyond a password, often a code from an authenticator app. Workspace owners can require it for all members to reduce account compromise risk.

Workspace-level controls governing authentication, link sharing, guest access, and data export. Owners use these to enforce policies consistently across all members and content.

A record of administrative and security-relevant events in a workspace, such as permission changes, member additions, and exports. It supports investigations and compliance reviews.

The policies and practices that control how workspace content is created, accessed, retained, and removed. It aligns Notion usage with organizational compliance and privacy obligations.

Rules defining how long content and activity records are kept before deletion. Retention settings help meet legal requirements and limit unnecessary storage of sensitive information.

The geographic location where workspace data is stored. Organizations with regional requirements select a storage region to satisfy local regulations and internal policies.

The top workspace tier that unlocks advanced controls such as SSO, SCIM, audit logs, data residency, and granular permissions. It targets larger organizations with compliance needs.

The fundamental content unit in Notion, capable of holding text, blocks, subpages, and embedded databases. Pages can be nested to form a hierarchy and carry their own permissions.

The smallest content element on a page, such as a paragraph, heading, image, or database view. Blocks can be moved, nested, and transformed into other block types.

A page nested inside another page, forming a parent-child relationship. Subpages typically inherit permissions unless access is changed explicitly.

A structured collection of pages with shared properties, displayed as tables, boards, calendars, or lists. Databases support filtering, sorting, relations, and multiple views.

A typed field on a database that stores information for each entry, such as text, select, date, person, or relation. Properties define the schema and enable filtering and sorting.

A saved presentation of a database with its own layout, filters, sorts, and visible properties. Multiple views let different teams see the same data in different ways.

A property that links entries between two databases, optionally two-way. Relations connect related records and support rollups and linked views.

A property that aggregates values from related database entries, such as a count or sum. Rollups summarize linked data without manual calculation.

A computed property that derives values from other properties using expressions and functions. Formulas enable calculations like totals, dates, and conditional outputs.

A reusable page or database entry layout that pre-fills structure and default property values. Templates standardize recurring content such as meeting notes or project briefs.

A predefined entry pattern applied when adding a new record to a database. It can set default property values and include a prepared body layout.

The organized hierarchy of teamspaces, pages, and databases that reflects how an organization works. Good structure improves navigation, discoverability, and permission clarity.

A shared area within a workspace that groups pages and databases for a team, with its own members and permission settings. Teamspaces separate access between departments or projects.

The mechanism that holds deleted pages and databases for a period before permanent removal. Users can restore items from trash, and administrators can manage retention behavior.

An action that creates a copy of a page or database, including its content and optionally subpages. Duplication helps reuse structures but may copy sensitive content to new locations.

Built-in assistant features that can draft, summarize, translate, and answer questions about workspace content. Availability and data handling depend on workspace plan and settings.

A Notion AI capability that answers questions using content the user already has access to. It respects permissions and surfaces relevant pages and databases as sources.

A database view condition that limits which entries are displayed based on property values. Filters are saved per view and can combine multiple conditions.