Documents often fail when they become separated from work. A process description lives on one page, tasks in another application, attachments in email and the report in a spreadsheet. Apexloop uses document pages as work centres that can hold text and live data side by side.
A page is therefore not an archive. It is a place where the team reads context, sees the current state and triggers next actions.
What a page can contain
A document page handles standard text blocks, headings, separators and media. Beyond that it can contain a database component with multiple views, a dashboard, a QR code with settings, buttons, links to records and shortcuts to other pages.
In practice, this means the team home page can show priorities, today's deadlines, pending approvals and links to the most-used processes. A project page can combine the brief, timeline, task subgrid, files and a button to create a report.
When to use a document page link column
Some content belongs directly to a specific record. A task brief, project specification, meeting notes or newsletter content are good examples for a document page link column.
The grid then holds concise values like status, deadline, owner and type. The record detail opens a rich document that can grow without the table becoming an unreadable wall of text.
A page can be a template
A document page can serve as a template for print or export. Automation substitutes placeholders like {{customer}}, {{invoice_number}} or {{total_amount}} into it. The result can be a PDF invoice, proposal, handover protocol or internal report.
The same principle works for newsletters. Content is created in the document editor, the campaign record holds status and date, and automation converts the page to email-safe HTML.
Buttons keep actions in context
A button block on a page or a button column on a record can open a URL or trigger automation with the context of the current record. This is important for processes where the user shouldn't have to think about where to click next.
Examples:
- create a PDF proposal,
- send an email to the customer,
- create a follow-up project,
- recalculate or check status,
- call an integration webhook.
A page should have an owner
The best work centres have a clear owner. That person doesn't have to write everything, but ensures the page reflects how the team actually works. If the page shows live views and dashboards, maintenance is simpler: less copying and more linking to actual data.
A good document page answers the question: "What do I need to know and what can I do right here?"