Pages is a no-code workspace that blends documents, spreadsheets, and databases into a single flexible canvas. Teams use it to build internal tools, wikis, and lightweight apps without writing code.
Each Page works like a smart page on the web, where blocks handle content, data, and interactions in a structured, shareable layout.
| Aspect | Details | Impact | Best Practice |
|---|---|---|---|
| Core Concept | Multi-block workspace combining docs, databases, and apps | Unifies knowledge and operations in one place | Use templates to launch common workflows quickly |
| User Interface | Block-based editor with sidebar for data and settings | Low learning curve for new users | Customize toolbar for frequent actions |
| Collaboration | Real-time editing, comments, and permissions | Improves team alignment and reduces email threads | Set clear role-based access per page |
| Integrations | Connects with Slack, GitHub, Google Workspace, and APIs | Extends reach across the tech stack | Use native automations for repetitive tasks |
Getting Started with Pages
The Getting Started with Pages section walks new users through the essentials of creating, organizing, and sharing their first pages. You begin by choosing a template or blank canvas, then add blocks such as text, tables, and databases.
As you build, you can link data between databases, set property filters, and create rollups to surface key information. These early setup choices determine how easily the page scales as your team grows.
Building Databases and Relations
Building Databases and Relations focuses on how to structure interconnected data using linked properties and relation columns. Each database can store records, define views, and power the rest of the page with dynamic content.
Relations let you connect customer records to deals, tasks to owners, and support tickets to products. Well-designed relations reduce duplication and make it easy to generate cross-database reports.
Automations and Workflows
Automations and Workflows show how to trigger actions automatically when data changes. You can send Slack notifications, update status fields, or create new records based on rules tied to form submissions or scheduled intervals.
By aligning automations with standard operating procedures, teams reduce manual steps and improve consistency. Start with simple two-step flows, measure their impact, and then expand to more complex multi-step workflows.
Permissions and Security
Permissions and Security explain how to control who can view, comment, or edit each page and database. Granular permissions at the page, row, and even cell level help protect sensitive information.
Use private pages for confidential strategy work, and public sharing for status dashboards. Combine role-based access with SSO to enforce security across the organization.
Scaling Pages for Team Use
- Define a small set of core databases to avoid fragmentation
- Use consistent property names and relation types across pages
- Leverage templates for onboarding, projects, and operations
- Set up automations for repetitive updates and alerts
- Audit permissions quarterly to maintain security and clarity
- Document data models so new users can navigate quickly
- Monitor performance by reviewing view configurations and indexing
FAQ
Reader questions
How does Pages differ from a traditional wiki or document editor?
Pages combines live databases, relations, and automations with document editing, enabling interactive apps rather than static content.
Can I connect Pages to external tools like Slack or GitHub?
Yes, native integrations and API support let you sync data, trigger notifications, and automate tasks across your stack.
What happens to my data if I change or delete a relation between databases?
You can choose to keep, clear, or reconnect records, and the platform logs changes so teams can review and roll back if needed.
How are permissions enforced when a page is shared publicly or via link?
Public links respect page-level and role-level settings, so admins can restrict edits, require sign-in, or allow anonymous view-only access.