# Notion App Feature and UI UX Specification

## Executive summary

Notion is a block-based workspace available on desktop, web, and mobile, organized around pages, databases, views, and collaboration controls. Its most distinctive product model is that nearly everything is either a page or a block on a page, while databases are collections of pages enriched with properties, multiple saved views, filters, sorts, groups, formulas, relations, and rollups. Official documentation now also references data sources as a first-class concept in the product and developer platform, indicating a deeper separation between database containers and underlying structured sources in newer API versions. citeturn11search0turn19view0turn18view0turn20view0turn44search11turn44search8

Across platforms, the UX is intentionally consistent in information architecture but not identical in interaction model. Desktop and web emphasize hover-revealed controls, keyboard accelerators, tabs, side peeks, and deep settings access. Mobile prioritizes compact navigation, persistent tap targets, a keyboard-adjacent editing toolbar, and reduced administrative scope. Official docs explicitly note that mobile has no hover states, collapses desktop column layouts into a single column, and does not support some actions such as imports, many account and billing changes, or workspace security editing. citeturn31view0turn31view1turn24search8

The discoverable feature surface is broader than classic note-taking. In addition to writing, blocks, and databases, Notion includes forms, charts, buttons, database automations, page analytics, sites publishing, a web clipper, external embeds, public and internal API connections, webhook actions, AI connectors, and MCP-based AI-app access. Enterprise layers add SAML SSO, SCIM, audit log, domain verification and management, security/compliance connections, private teamspaces, and advanced workspace controls. citeturn16view2turn21view0turn16view3turn26search2turn23search8turn40search7turn39search8turn41view0turn41view1turn41view2turn41view3turn22view5turn22view6turn16view9turn29view1turn40search18

From a UI/UX standpoint, Notion uses a sparse, high-density interface with progressive disclosure. Block handles, slash commands, view settings, peek modes, page-level menus, and sidebar nesting let novices start with plain text and gradually discover advanced behaviors. The design relies heavily on hover affordances, contextual menus, command/search entry points, drag-and-drop blue placement guides, and modal or side-peek editing surfaces. Official docs are good on user-facing behavior, but they do **not** publish a full formal design system, component token inventory, animation timing spec, or ARIA role map. Where those details are not public, this report marks them as **unspecified**. citeturn11search0turn22view3turn18view0turn34view0turn35view0turn31view0

Accessibility and localization are mixed. Officially, Notion supports extensive keyboard shortcuts, dark/light/system appearance, many interface languages, mirrored UI for Arabic and Hebrew, block-level text direction, and RTL auto-detection in most text blocks except simple tables. However, public official documentation does not publish WCAG conformance tables or ARIA implementation details, and independent accessibility reviews have reported issues in desktop flows involving contrast, alt text, and tabbing. The most defensible conclusion is that accessibility support exists and is improving, but a complete component-level accessibility spec is **not publicly discoverable**. citeturn34view0turn36view0turn36view2turn24search0turn12search10turn32search15

## Research basis and product model

This report is grounded primarily in Notion’s Help Center, official pricing and product pages, official developer documentation, public release/changelog material, public app-store listings, and public product screenshots/help screenshots. Third-party material is used only where official sources are silent, most notably for accessibility gaps. Because the Notion product changes frequently and some behaviors are controlled by plan, workspace policy, or experimental rollout, the catalog below focuses on what is **publicly documented or directly visible in public materials** as of July 2026. Details not described by those sources are labeled **unspecified** rather than inferred as fact. citeturn29view1turn24search4turn44search12turn14search0turn14search1turn12search10turn32search15

At the model level, Notion can be understood as a hierarchy of workspace containers, navigational surfaces, content pages, composable blocks, and structured databases. Pages can contain freeform blocks, inline databases, linked databases, forms, charts, embeds, comments, backlinks, and page discussions. Database entries are themselves pages, which is why table rows, board cards, calendar items, and gallery cards all open into full page bodies with additional content and properties. citeturn22view7turn11search0turn16view7turn16view2turn21view0turn18view0

```mermaid
flowchart LR
    Workspace --> Sidebar
    Sidebar --> Favorites
    Sidebar --> Teamspaces
    Sidebar --> Shared
    Sidebar --> Private
    Teamspaces --> Pages
    Shared --> Pages
    Private --> Pages
    Pages --> Blocks
    Pages --> Subpages
    Pages --> Databases
    Databases --> Views
    Databases --> Properties
    Properties --> Formula
    Properties --> Relation
    Relation --> Rollup
    Databases --> Templates
    Databases --> Automations
    Databases --> Forms
    Databases --> Charts
    Pages --> Comments
    Pages --> Backlinks
    Pages --> Publish
```

The same structure also explains why Notion’s permission model is unusually granular. Pages can be shared directly, accessible through teamspaces, exposed via general access, or published to the web; database pages can additionally use row/page-level access rules based on people properties; and API connections inherit a page-scoped access model that closely mirrors human sharing. citeturn42view0turn41view1

The chart below is an analytical grouping used for this report, not a vendor taxonomy.

```mermaid
pie showData
    title Analytical grouping of discoverable Notion feature families
    "Core authoring and page composition" : 24
    "Structured databases and analytics" : 26
    "Collaboration and permissions" : 18
    "Integrations and developer platform" : 16
    "Admin, security, and billing" : 16
    "Platform-specific and UI UX behaviors" : 20
```

## Exhaustive feature catalog

### Core authoring, page, and content features

| Feature family | Discoverable capabilities | Notes |
|---|---|---|
| Page fundamentals | Top-level pages, nested subpages, page titles, icons, covers, breadcrumbs, favorites, link-to-page blocks, page links via `@`, `[[`, and `+` commands. | Pages are the primary content unit; pages can live in teamspaces, shared, private, or favorites sections. Breadcrumb blocks and page links are official block-level features. citeturn22view7turn22view3turn11search0turn35view0 |
| Basic blocks | Text, page, to-do, headings, simple table, bulleted list, numbered list, toggle list, quote, divider, link to page, callout. | Official block menu documentation lists these as native block types. Toggles currently must be opened/closed manually; official docs note no “open or close all by default” setting in that page. citeturn11search0 |
| Media and code blocks | Image, video, audio, file, code block, PDF, bookmarks, embeds, equations. | Media can be uploaded or embedded; code blocks support languages and formatting; equations support TeX. citeturn11search0turn41view0turn35view0 |
| Advanced page utilities | Table of contents, breadcrumbs, button blocks, synced blocks, inline equations, reminders and date mentions. | Buttons can insert blocks, add pages, edit pages, send notifications, send Gmail mail, send webhooks, and show confirmations; synced blocks replicate shared content across locations. citeturn16view3turn16view6turn11search0 |
| Text styling and layout | Rich-text selection toolbar, bold, italics, underline, strikethrough, inline code, links, comments, text color/highlight, three typography styles, small text, full width. | Page-level style controls include Default, Serif, and Mono; layout toggles include small text and full width. citeturn36view3turn11search0 |
| Page customization | Backlinks visibility, page discussions toggle, database-page heading customization, inline comment display mode, database-page layout builder with pinned properties, property groups, modules, and side panels. | Some of these controls are page-type specific; database pages expose deeper layout controls than standard pages. citeturn24search7turn16view8 |
| History and lifecycle | Version history, restore previous versions, archive/unarchive, trash and restore, workspace export backups. | Version history is page-level; archive shows a yellow banner; workspace exports send a download link by email; public docs distinguish trash restore from version restore. citeturn23search0turn23search12turn28view2 |

### Structured databases, properties, views, and analytics

| Database capability | Discoverable scope | Notes |
|---|---|---|
| Database object model | Databases are collections of pages; rows/cards/items are pages that open into full page bodies. | This is foundational to Notion’s data model and drives uniform editing across table, board, list, calendar, and gallery surfaces. citeturn18view0turn15search9 |
| View types | Table, Board, Timeline, Calendar, List, Gallery, Chart; forms are connected to databases. | Chart view supports vertical bar, horizontal bar, line, donut, and number charts; forms store responses in a database and create a default `Responses` table view. citeturn17view2turn21view0turn16view2 |
| View settings | Layout, property visibility, filter, sort, group, sub-group, copy link to view, open pages in side peek/center peek/full page. | View tabs can be reordered; view-tab display can be icon only, text only, or both, but that preference is personal to the viewer. citeturn18view0 |
| Filters and advanced filters | Simple filters, personal vs save-for-everyone filters, advanced filters with nested `AND`/`OR` groups up to three layers deep. | Sub-item visibility can affect filtered results. citeturn18view0 |
| Sorts and groups | Multi-sort, alphabetic/numeric/select-order sorting, manual group sorting, hide empty groups, sub-grouping. | Table columns can be frozen for comparison during horizontal scrolling. citeturn18view0 |
| Database search | Title-and-property search within databases that have at least three pages. | Search narrows results as you type. citeturn18view0 |
| Conditional color | Rule-based page background color based on property conditions. | Requires content-edit or stronger permissions to configure; viewers without edit rights can still see the color. citeturn19view0 |
| Property types | Text, Number, Select, Status, Multi-select, Date, Formula, Relation, Rollup, Person, File, Checkbox, URL, Email, Phone, Created time, Created by, Last edited time, Last edited by, Button, ID, Place. | Official docs describe 22 property types and note a database limit of up to 500 properties to preserve performance and reliability. citeturn19view0 |
| Property behaviors | Date ranges, reminders, timezone/date-format control, select-option editing, multi-file fields, person tagging, direct property comments, show/hide by view. | Property comments appear in database pages; some property-type settings are type-specific, such as text wrapping or select-option order. citeturn19view0 |
| Relations | One-way or two-way relations, self-relations, relation display options, shown/hidden properties for related pages, optional one-page limit. | Relations connect pages across databases and can surface related-page properties inline in the relation field. citeturn20view0 |
| Rollups | Aggregation over related pages, including showing originals, unique values, counts, sums, and other calculations. | Rollups depend on an existing relation, then choose relation property, target property, aggregation, and formatting. citeturn20view0 |
| Formulas | Formula properties operate over database properties, built-ins, operators, dates, lists, and style/text functions. | Official docs describe properties, built-ins, operators, list functions such as `map`, `filter`, `find`, `some`, `every`, and style functions such as `style()` and `unstyle()`. citeturn16view4turn16view5turn37view1turn37view3turn37view4turn37view5 |
| Linked databases | Linked views of the same database can appear across multiple pages with different filters and sorts. | This is a canonical dashboard pattern in Notion. citeturn16view7turn18view0 |
| Database templates | New-page templates, repeating templates, nested templates with limits, edit/duplicate/delete template actions. | Repeating templates can recur daily, weekly, monthly, or yearly; nested recurring templates have depth and cadence limits. citeturn38search2turn38search0 |
| Database automations | Trigger-and-action automations on paid plans; Slack notifications on Free; variables, formulas, Gmail send, webhook send, property edits, page creation, notifications. | Automations cannot trigger other automations, but button actions can trigger database automations. Slack automations can only be edited by their creator. citeturn26search2turn27search10 |
| Charts | Bar, line, donut, number charts; configurable axes, visible/hidden groups, cumulative mode, legends, labels, style palettes, drilldowns. | Charts cannot edit database entries directly; large databases may update more slowly; chart groups/subgroups have published display limits. citeturn21view0 |
| Forms | Form builder with title, description, icon, cover, required questions, descriptions, list/dropdown presentation, response settings, shareable submission flow. | Form question names typically sync to database property names; form-view export is not supported. citeturn16view2turn28view1 |
| Granular row access | Database page-level access rules based on people or created-by properties. | Available on Business and Enterprise; applies across all views, including linked views. citeturn42view0 |

### Integrations, API surface, embeds, and external content

| Integration surface | Discoverable capabilities | Notes |
|---|---|---|
| Native/embed surface | Embeds from 1,900+ domains via Iframely; common examples include Framer, Figma, Loom, Miro, Typeform, Google Maps, GitHub Gist, Excalidraw, and many more. | If a source site blocks embeddability, Notion shows a `Failed to Load` error. Link previews and bookmarks are distinct surfaces in the embed family. citeturn41view0turn11search1 |
| Workspace connections | Members and owners can add connections in `Settings → Connections`; those connections can then be attached to particular pages/databases from the page `•••` menu. | Enterprise can restrict who can add and page-connect connections; page disconnection is exposed inline in the page menu. citeturn41view1 |
| Notion API | Official REST/developer platform exposing Authentication, Blocks, Pages, Databases, Data sources, Comments, Views, File uploads, Search, Users, and Custom emojis. | API is versioned by date and requires the `Notion-Version` header; latest public version in the cited documentation is `2026-03-11`. citeturn44search0turn44search4turn44search11 |
| API pagination and limits | Cursor-based pagination; search/list endpoints paginate; default list size is 10 in the introduction docs. | Request limits include a per-connection average of 3 requests/sec plus a per-workspace limit scaled to plan; 429 `rate_limited` and 529 `service_overload` responses should be retried/backed off. citeturn44search12turn44search0 |
| API webhooks | Connection webhooks deliver real-time HTTP POST events for pages, databases, data sources, comments, file uploads, and views. | Official webhook docs position this as an alternative to polling and document verification-token setup and event subscriptions. citeturn44search1turn44search3 |
| No-code and low-code automation | Zapier and Make are explicitly supported through Notion’s connection marketplace and webhook actions, alongside more general partner connections. | Notion’s own guides also recommend webhook actions with platforms like Zapier and Make. citeturn27search1turn27search2turn27search9turn27search8 |
| AI connectors | Cross-app search and answer retrieval from Slack, Google Drive, Jira, Gmail, Notion Mail, MS Teams, SharePoint/OneDrive, GitHub, Outlook, Notion Calendar, Linear, and Google Calendar. | Available from Business/Enterprise for third-party apps; Notion Mail and Notion Calendar connectors are available on all plans. Search surface appears in AI chat, sidebar AI, and sidebar Search. citeturn41view2 |
| MCP access | Notion MCP connects AI apps such as Claude, ChatGPT, and Cursor to read from and write to Notion. | This is distinct from AI connectors; MCP is documented as AI-agent-oriented workspace access. citeturn41view3 |
| Web clipper | Browser extension for Chrome and Safari on desktop saves web content into Notion. | Saved pages can populate databases and carry imported text/images from web pages. citeturn39search8turn33image1 |

### Import, export, backup, sites, and portability

| Portability capability | Discoverable behavior | Notes |
|---|---|---|
| Imports | Desktop and web only; direct file imports include TXT, Markdown, DOCX, CSV, HTML, PDF, ZIP, plus app imports such as Confluence, Asana, Evernote, and Trello. | The import UI tracks upload size, time, and status. Mobile import is explicitly unsupported in official help docs. citeturn28view0turn31view0 |
| Page/database export | PDF export from desktop and mobile; export modal allows page-format and inclusion choices. | PDF export can fail over to HTML; form view cannot be exported, and users are told to export the equivalent table instead. citeturn28view1turn16view2 |
| Full workspace export | HTML, Markdown, CSV for databases, uploaded files, and on Business/Enterprise also workspace-wide PDF export. | Whole-workspace export is desktop/web only and sent as an emailed link expiring after seven days; inaccessible/private pages not available to the exporter are excluded. citeturn28view2turn30view3 |
| Member export | Business and Enterprise can export workspace members as CSV with email, names, role, permission groups, and user ID. | Administrative portability feature for governance and audits. citeturn30view3 |
| Backups | Official help says Notion keeps per-minute backups of page content on its server; security docs also say automated backups of all customer/system data are enabled and monitored, with daily minimum backup cadence. | The two statements are not contradictory, but they describe different layers of backup policy; exact retention architecture is not fully specified publicly. citeturn28view2turn29view0 |
| Notion Sites | Pages can be published to the web; plans add custom site controls, branding removal, analytics integrations, and domains. | Free includes unlimited sites, one `notion.site` domain claim, and search indexing; Plus adds custom sites, and custom domains are an add-on with billing aligned to workspace billing cadence. citeturn40search7turn25search7turn25search10 |

## Collaboration, administration, security, and billing

### Collaboration, sharing, comments, mentions, and activity

Notion’s collaboration model combines page sharing, role-based permissions, live presence, comments, mentions, notifications, suggestions, and historical activity. Official docs state that unlimited people can edit the same page at once, with avatar presence tracking where collaborators are reading or editing. The page updates surface highlights additions in blue, removals in gray strikethrough, and can also show comments and revisions over time. citeturn22view1

The `Share` menu is the central collaboration control. From there, users can invite individuals or groups, share with a teamspace, copy links, publish to the web, assign access levels, and set general access to `Only people invited`, `Everyone at {workspace}`, or `Anyone on the web with link`. Public links can expire, and Enterprise workspaces can disable publishing/public links altogether. citeturn42view0

Permission levels are explicitly differentiated. Notion documents `Full access`, `Can edit`, `Can edit content` for databases, `Can create` for submit-only database contribution on Business/Enterprise, `Can comment`, and `Can view`. This means Notion’s access model is not just “viewer/editor,” but a layered mix of document and structured-data permissions. citeturn42view0

Comments can be attached to selected text, blocks, and properties; mentions can target people, pages, dates, and reminders; replies and mentions route into Inbox and optional email, push, desktop, and Slack notifications. Users can also configure page-specific notification scope, such as `All comments`, and desktop meeting-detection notifications can prompt AI Meeting Notes under certain conditions. citeturn11search0turn35view0turn36view1turn22view2

Page analytics extend activity visibility. Owners and editors can open `••• → Updates & analytics → Analytics` to see total and unique views over time as well as who created, edited, or viewed the page and when. Workspace-level settings can also toggle whether page view analytics are saved and displayed. citeturn40search1turn30view2turn30view3

### Teamspaces, members, guests, groups, and organization features

| Governance surface | Discoverable behavior | Notes |
|---|---|---|
| Workspace roles | Workspace owner, membership admin, member, guest; temporary members for consultants are also documented. | Temporary members do not consume a paid seat and can have expiration dates up to one year. citeturn25search0turn25search6 |
| Guests | Guests are external collaborators invited to specific pages. | Guest additions can be blocked by guest limits, workspace/teamspace settings, or allowed-domain policies; on some Enterprise configurations, inviting a guest can convert them to a member. citeturn42view0 |
| Groups | Notion supports permission groups for more granular sharing and teamspace membership. | Official group-management details are distributed across member and teamspace docs rather than a single product spec. citeturn25search11turn40search12 |
| Teamspaces | Dedicated collaborative spaces with open, closed, private, and default variants. | Default teamspaces auto-include all workspace members; private teamspaces are available on Business and Enterprise. citeturn40search2turn40search6turn40search8turn40search16 |
| Allowed email domains | Workspaces can set trusted/allowed domains so users with matching emails are prompted to join automatically. | On paid plans, domain-joined members affect billing. citeturn30view0turn30view1 |
| Workspace export and analytics | Owners can export all workspace content, export members CSV, and toggle page analytics visibility. | Many of these settings are unavailable on mobile and restricted to admins/owners or certain plans. citeturn22view4turn30view3 |
| Enterprise security controls | Disable publishing/forms, disable export, disable moving pages to other workspaces, restrict guest/member requests, configure restricted-member rules, choose trash-retention behavior. | These settings are surfaced in `Settings → Security` and are documented as Enterprise-only for the deeper controls. citeturn30view2 |
| Domain verification and management | Business adds domain verification; Enterprise adds domain management actions such as claim, transfer-request, or delete for workspaces on the verified domain. | These are plan-differentiating organization features, not just cosmetic settings. citeturn29view1 |

### Security, privacy, auditability, and billing

Security documentation states that customer data is encrypted at rest using AES-256 and in transit using TLS 1.2 or greater; Notion is hosted on AWS; critical-system logging is enabled; backups are monitored; threat modeling, code review, security scans, penetration testing, and bug bounty/responsible disclosure are part of the application security program. citeturn29view0

Business and Enterprise plans add federated identity and governance. SAML SSO is documented for Business and Enterprise, while SCIM user-and-group provisioning is Enterprise-only. Enterprise also adds audit log, advanced security and controls, zero data retention with LLM providers for Enterprise AI use, domain management, and security/compliance connections for SIEM and DLP workflows. citeturn22view5turn22view6turn29view1turn40search18

The audit log is broad. Official help categorizes events into page, workspace, workers, account, teamspace, form, and data-source events, including page edited, property edited, page viewed, page created, page suggestions created/accepted/rejected, comments read by external AI tools, page locked/unlocked, and other security-relevant events. citeturn16view9turn23search13

Billing is seat-based for members rather than guests. Official billing docs explain that workspace owners can track paid seats and member counts in `Settings → People`, and that adding or removing members changes usage against seats rather than charging every time a specific human identity changes. Public pricing also distinguishes Free, Plus, Business, and Enterprise plan bundles with increasingly advanced collaboration, charts, files, connections, AI, row-level permissions, private teamspaces, SSO, SCIM, audit log, and domain controls. citeturn25search2turn25search3turn29view1

A concise plan comparison focused on app capabilities is below.

| Plan | Key app capabilities publicly emphasized |
|---|---|
| Free | Basic forms, basic sites, Notion Calendar, Notion Mail sync, databases with subtasks/dependencies/custom properties, trial AI, one chart trial. citeturn29view1turn25search5 |
| Plus | Custom forms, custom sites, unlimited charts, unlimited collaborative blocks, unlimited uploads, basic connections. citeturn29view1 |
| Business | Agent, AI Meeting Notes, Enterprise Search beta, SAML SSO, granular database permissions, verified pages, private teamspaces, domain verification, premium connections. citeturn29view1 |
| Enterprise | Zero data retention with LLM providers, SCIM, advanced security controls, audit log, SIEM/DLP connections, domain management, additional connection options. citeturn29view1turn40search18 |

## UI UX specification

### Layout patterns, navigation surfaces, and responsive structure

Notion’s cross-platform layout uses a persistent hierarchical navigation model, but the container chrome changes by platform. Desktop and web center on a left sidebar with sections such as Favorites, Teamspaces, Shared, and Private, plus page nesting, drag-reordering, and sidebar collapse/resize. Database views expose tab-like view selectors and top-right settings affordances, while pages expose a title area, collaborator avatars, share control, overflow menu, and contextual block handles inside the content canvas. citeturn22view3turn30view5turn15search3turn18view0

Mobile keeps the same conceptual structure but compresses it into tap-first navigation. Official docs note that hover-revealed controls disappear, columns collapse into one column, and editing controls move to a toolbar near the keyboard. The mobile shell also exposes `+` and `•••` icons persistently rather than relying on cursor hover. citeturn31view0turn11search0

The public screenshots below illustrate the consistent information architecture across desktop and mobile, the database-centric learning flow, and the compressed mobile database UI.

iturn33image0turn33image2turn33image1turn33image3

On desktop specifically, Notion adds tabbed browsing, new windows, tab hover previews, and a global Command Search surface accessible even outside the foreground app. Official docs describe smooth tab switching, optional “open search when creating a new tab,” and customizable keyboard shortcuts for global command search, along with menu-bar/task-bar presence and optional open-at-login behavior. citeturn31view1turn34view0

The overall navigation flow can be reduced to a small set of repeated patterns.

```mermaid
flowchart TB
    Launch --> Sidebar
    Sidebar --> ExistingPage
    Sidebar --> NewPage
    ExistingPage --> PageHeader
    PageHeader --> ShareMenu
    PageHeader --> OverflowMenu
    ExistingPage --> ContentCanvas
    ContentCanvas --> SlashMenu
    ContentCanvas --> BlockHandleMenu
    ExistingPage --> InlineDatabase
    InlineDatabase --> ViewTabs
    ViewTabs --> PeekOpen
    PeekOpen --> SidePeek
    PeekOpen --> CenterPeek
    PeekOpen --> FullPage
    Sidebar --> Search
    Search --> JumpToPage
    Search --> NewTab
    Search --> AIChat
```

### Component-level UI specification

The table below catalogs the major discoverable UI elements, their states, and their main behaviors. Where a state is not documented in public materials, it is marked **unspecified**.

| Component | Principal states | Main interactions | Platform notes |
|---|---|---|---|
| Sidebar | Expanded, collapsed, resized, section-collapsed, drag-reordered. | Resize by dragging edge; collapse with `<<`/`>>`; drag pages to reorder/nest; hover reveals `+` and `•••` on pages and teamspaces. citeturn22view3turn15search0 | Sections include Favorites, Teamspaces, Shared, Private; views for full-page databases appear nested with a dot marker. citeturn30view5turn18view0 |
| Page header | Normal, collaborative-presence, published, archived, analytics-enabled. | Title editing, icon/cover set, share, `•••`, collaborator avatars, updates/history access. citeturn15search3turn42view0turn23search8turn23search12 | Archived pages surface a yellow banner; official archive-state spec is page-level. citeturn23search12 |
| Block handle region | Resting, hover-revealed, selected, drag-active. | `+` opens block inserter; `⋮⋮` opens block actions or allows drag; blue guides appear on drag target placement. citeturn11search0 | Mobile replaces hover with persistent tap-first controls. citeturn31view0 |
| Slash menu | Closed, open, filtered by query, dismissed. | Type `/` then block or action name; can add blocks, transform blocks, color text, invoke embeds, buttons, TOC, math, and more. `Esc` dismisses. citeturn11search0turn35view0 | Official mobile docs say there are no slash commands on mobile editing; mobile uses the editing toolbar instead. citeturn11search0turn31view0 |
| Database toolbar | Viewing, filters open, sorts open, groups open, properties open, layout open. | Create/switch views, toggle property visibility, filter/sort/group, set open mode, copy link to view, search, freeze columns. citeturn18view0 | Different layouts default to different page-open modes: side peek for table/board/list/timeline, center peek for gallery/calendar. citeturn17view0turn17view2 |
| View tabs | Default, reordered, icon-only, text-only, icon+text. | Drag to reorder; change personal display style. citeturn18view0 | Personal preference only; not global for all users. citeturn18view0 |
| Peek surfaces | Side peek, center peek, full page. | Open database rows/cards/pages into chosen presentation. citeturn18view0 | Systematically used to preserve context while editing structured items. |
| Share panel | Invite, general access, publish, role-change, link-expiry, remove access. | Invite members/groups/guests, set access levels, publish to web, create expiring public links, stop sharing. citeturn42view0 | Database pages add row-level/page-level access rules in Business/Enterprise. citeturn42view0 |
| Search and Command Search | Inline quick find, global command search, AI search augmentation. | `cmd/ctrl + P` or `K`, jump to recent page, create page, start AI chat, search from menu bar/task bar. citeturn34view0turn31view1turn41view2 | Desktop-only global command-search shell is documented; full equivalent is unspecified for web. |
| Inbox and notifications | Badge idle, unread badge, inbox list, email/push/desktop delivery. | Mentions, replies, reminders, person-property assignments, page updates. citeturn36view1turn22view2 | Mobile settings route through `Settings → My notifications`; desktop includes badge icons and meeting-detection notifications. citeturn24search5turn24search9 |
| Comments and discussions | Inline visible, minimal inline count, property comment, page discussion. | Add comment to text with selection toolbar or shortcut; property comments in database pages; page discussions configurable in page customization. citeturn11search0turn19view0turn24search7 | Public docs do not publish a complete statechart for moderation or resolution; partially unspecified. |
| Forms | Builder, question-hover menu, required-on/off, description-on/off, shareable response mode. | Add title/description/icon/cover, add questions, set required, choose list/dropdown for multi-choice, map to database properties. citeturn16view2 | Exporting the form view itself is unsupported. citeturn16view2turn28view1 |
| Settings surfaces | Workspace-general, account, preferences, notifications, security, connections, AI. | Access from workspace switcher down-arrow or settings entry points; configure appearance, language, notifications, connections, domains, exports, billing, and security. citeturn36view0turn24search5turn22view4turn41view1turn41view2 | Many advanced workspace settings do not appear in mobile. citeturn22view4turn31view0 |

### Microinteractions, discoverability, empty states, and error states

Notion’s discoverability strategy is heavily contextual rather than explicit. New users encounter a blank page plus a slash menu, a left-margin `+`, and block handles; when they create databases, they encounter view tabs, a settings icon, page peeks, and the `New` button/dropdown for templates. Database views can be linked into pages, and full-page database views appear nested in the sidebar, reinforcing navigation discoverability through repetition. citeturn11search0turn15search2turn18view0turn16view7

Official docs also expose several “empty-state” launch patterns. Creating a new page from the sidebar opens a preview mode where users can start typing before deciding final placement. The template gallery is explicitly positioned as a starting point for structure when users are unsure how to begin. Import and chart flows also present staged creation prompts rather than blank-screen dead ends. Public docs do **not** enumerate every empty state across the product, so a complete empty-state inventory is **unspecified**. citeturn15search0turn38search17turn28view0turn21view0

The most visible microinteractions documented publicly are hover-revealed controls, drag-and-drop blue guides, smooth tab switching, tab hover preview on desktop, live collaborative cursors/presence, chart hover labels, comment/revision highlighting in updates, and notification badges. Official docs describe these behaviors but do **not** publish animation durations, easing curves, or haptic/motion token values; those remain **unspecified**. citeturn11search0turn22view1turn31view1turn21view0

Notion’s documented error states are functional rather than theatrical. Examples include `Failed to Load` for blocked embeds, exclamation-mark failure state and auto-pause for failed webhook automations, property-count-limit errors at 500 properties, unsupported export from form view, unsupported import on mobile, and archive-state warning banners. The public help center does not expose a complete platform-wide error taxonomy, so an exhaustive error catalog is **unspecified**. citeturn41view0turn27search8turn19view0turn16view2turn31view0turn23search12

### Keyboard shortcuts and command surfaces

Notion is unusually keyboard-forward. Official docs say shortcuts cover navigation, creation, styling, block movement, slash commands, mentions, page linking, toggles, comments, zoom, table fills, and block transformations. The international keyboard story is still incomplete: Notion’s shortcut documentation explicitly says the published instructions are for English/QWERTY keyboards and that internationalization is on the roadmap. citeturn34view0turn35view0

A concise high-value shortcut catalog is below.

| Category | Shortcut examples | Effect |
|---|---|---|
| Search and navigation | `cmd/ctrl + F`, `cmd/ctrl + P` or `K`, `cmd/ctrl + [` and `]`, `cmd/ctrl + L` | Search within page, quick find / jump to recent page, back/forward, copy page URL. citeturn34view0 |
| Desktop shell | `cmd/ctrl + N`, `cmd/ctrl + shift + N`, `cmd/ctrl + T`, `cmd/ctrl + click`, `option + shift + click` | New page, new window, new tab, open link in new tab, open page in new window. citeturn34view0 |
| Theme | `cmd/ctrl + shift + L` | Toggle dark/light mode. citeturn24search0turn34view0 |
| Commenting and formatting | `cmd/ctrl + shift + M`, `B`, `I`, `U`, `shift + S`, `E`, `K` | Create comment, bold, italic, underline, strikethrough, inline code, add link. citeturn34view0 |
| Block manipulation | `Esc`, `cmd/ctrl + /`, `cmd/ctrl + D`, `cmd/ctrl + shift + arrows`, `cmd/ctrl + enter` | Select block, edit/change selected blocks, duplicate, move block, modify current block. citeturn35view0 |
| Hierarchy and nesting | `Tab`, `shift + Tab`, `cmd/ctrl + shift + U` | Nest, un-nest, go up one level in page hierarchy. citeturn34view0turn35view0 |
| Toggle control | `cmd/ctrl + option/alt + T` | Expand or close all toggles in a toggle list. citeturn35view0 |
| Database peek navigation | Mac `ctrl + shift + K/J`, Windows `ctrl + K/J` | Previous/next database page while in peek view. citeturn34view0 |
| Slash, mention, page-linking | `/`, `@`, `[[`, `+` | Block insertion/transformation, mentions/reminders, link/create pages, page creation-first alternate linking flow. citeturn35view0 |

## Platform differences, performance, accessibility, localization, and unspecified details

### Platform comparison

| Surface | Desktop app | Web app | Mobile app |
|---|---|---|---|
| Primary strengths | Distraction-free shell, tabs, windows, push notifications, Command Search outside foreground app. citeturn31view1turn34view0 | Broad access on supported browsers; deepest parity with desktop for general editing and admin tasks. citeturn39search2turn39search4 | Tap-first editing, reading, comments, AI access on the go, AI widget/shortcuts. citeturn31view0 |
| Interaction model | Hover-rich, keyboard-heavy, drag-heavy. citeturn11search0turn31view1 | Similar to desktop, browser-contained. citeturn39search2 | No hover; `+` and `•••` replace hover discoverability; columns collapse. citeturn31view0 |
| Tabs and windows | Yes, including new tab, new window, tab preview. citeturn31view1turn34view0 | Browser tabs/windows, but official “Notion tab” behaviors are desktop-specific. | Native app tabs/windows are **unspecified** in public docs. |
| Imports | Supported. citeturn28view0 | Supported. citeturn28view0 | Unsupported. citeturn31view0 |
| Admin/billing/security settings | Supported. citeturn22view4turn36view0 | Supported. citeturn22view4turn36view0 | Many are explicitly unavailable. citeturn31view0 |
| Theme/language | System/light/dark; language selector in Preferences. citeturn24search0turn36view2 | Same general settings surface. citeturn24search0turn36view2 | Appearance setting exists; language follows system ranking. citeturn24search0turn36view2 |
| Browser / runtime support | Native Mac/Windows app. citeturn31view1 | Chrome supported across last eight extended stable releases; Firefox, Safari, and Edge for last two major releases; Internet Explorer unsupported. citeturn39search4turn39search2 | iOS and Android native apps. citeturn31view0turn14search0turn14search1 |

### Performance and offline behavior

Public official performance documentation is selective rather than exhaustive. Notion has publicly documented Android launch-performance work and stated that the Android app launches more than twice as quickly as it did at the start of 2023. Official chart-view documentation also warns that charts in large databases may update more slowly, and database-property documentation explains that the 500-property ceiling exists to keep databases fast and reliable. citeturn14search11turn21view0turn19view0

A fully current, platform-by-platform offline specification is **not completely published** in today’s help-center materials. Public desktop and mobile help pages focus more on download, editing differences, and platform restrictions than on a full sync/conflict matrix. Accordingly, the safest conclusion is that offline behavior exists in some form for installed apps and cached content, but the exact rules for every block type, database interaction, view, and conflict condition are **partially unspecified in public documentation**. citeturn31view0turn31view1

### Accessibility and localization

Officially documented accessibility-related capabilities include dark mode, extensive keyboard shortcuts, Markdown shortcuts, interface-language selection, week-start preferences, RTL interface mirroring for Arabic and Hebrew, auto-detected text direction in most text blocks except simple tables, manual block-level text-direction controls, and an “always show direction controls” preference. citeturn24search0turn34view0turn36view2

What official docs do **not** publish is equally important: there is no public ARIA role inventory, no official WCAG conformance matrix, no keyboard focus-order specification, no contrast-ratio token sheet, and no screen-reader support matrix broken down by component. Those details are therefore **unspecified** in official public sources. citeturn24search4turn36view2

Unofficial accessibility analyses fill part of that gap, but should be treated as supplementary rather than normative. Independent public reviews from Pratt and Navya Thakkar’s assessment both reported issues in desktop flows involving contrast, alt text, and keyboard tabbing. That does not negate Notion’s documented keyboard and RTL features; it indicates the public accessibility picture is mixed and still incomplete. citeturn32search15turn12search10turn34view0turn36view2

Localization support is broad. The public language list includes English, English (GB), Japanese, French, German, Spanish (Spain), Spanish (Latin America), Portuguese (Brazil), Chinese simplified and traditional, Dutch, Norwegian, Swedish, Danish, Finnish, Korean, Vietnamese, Thai, Bahasa Indonesia, Arabic, Hebrew, and Italian. Help-center footers and download pages also visibly surface a similar multilingual set across product pages. citeturn36view2turn14search10turn18view0

### Explicitly unspecified or only partially discoverable details

The following details were **not** fully discoverable in current public official sources and should be treated as unspecified unless verified directly inside a live product build or private enterprise documentation:

The complete ARIA map and screen-reader announcement behavior for each component; animation timing tokens and easing curves; a full catalog of loading, error, and empty states; a fully up-to-date offline-sync matrix for web, desktop, and mobile across all block and database operations; exact parity tables for every minor mobile interaction; and a complete public design-system inventory for every primitive component, token, and spacing rule. This is not a weakness in the research process so much as a boundary of what Notion publishes openly today. citeturn24search4turn31view0turn31view1turn12search10turn32search15

Even with those gaps, the overall picture is clear. Notion’s public product surface is unusually deep: block-based authoring, page-centric knowledge management, database-driven workflows, rich permissions, multi-surface collaboration, strong customization, a serious developer platform, expanding AI access patterns, and a UI architecture that scales from plain-text note-taking to enterprise knowledge operations. The remaining uncertainty is concentrated not in major feature existence, but in the undocumented microscopic details of implementation. citeturn11search0turn18view0turn42view0turn41view1turn29view1