Document Editor
Blueputto Document Editor brings writing, structure, attachments, related records, and signature approvals into one single-document workspace.
Grzegorz
Document Editor is the single-document workspace in Blueputto. It brings together writing, structure, file handling, related records, and approval steps around one document instead of scattering them across separate screens.
That is what makes it the real center of document work. Teams enter from Documents, then stay inside one record while they draft, organize, attach, and send that document forward.
Writing happens in the main canvas
The core of the page is a large title field paired with a rich text editor. Blueputto uses a block-based editing surface, so users can draft longer content without leaving the record or opening a separate modal.
In the current implementation, the editor supports:
rich text editing,
inline image uploads,
direct document title editing,
save from the main actions area,
and keyboard save with
Ctrl+SorCmd+S.
The save flow is built around the record itself. If there are unsaved changes, the page can persist the current state without navigating away. If image uploads are still in progress, save is intentionally blocked so the document does not end up in a half-finished state.
Structure and record settings stay beside the content
The document page does not hide structure behind a separate settings screen. On desktop, the editor sits beside a dedicated side panel. On mobile, the same controls stay available above the content area.
The settings panel groups the rest of the record into focused sections, including:
document status,
author assignment,
reusable labels,
custom metadata fields,
file attachments,
related items,
recent document activity,
and signatures.
This matters because document work is rarely just writing. Teams often need to attach evidence, connect the document to an item record, apply labels, or add structured metadata before the record is actually useful.
The metadata section is especially important here. Users can add, rename, remove, and fill custom fields directly inside the document, which turns the record into something more structured than a plain rich text page.
Signatures turn the same record into an approval surface
Document Editor also holds the signature workflow for the current document. Teams can request signatures from internal members or external people, resend invitations, cancel a request, sign with OTP verification, and void a completed or in-progress signature flow when needed.
That keeps approval close to the document content instead of forcing a separate contract workflow tool.
In the current implementation, sending a document for signature also changes the editing mode. Once the document is no longer in draft, the content, core properties, and attached files become read-only. Metadata and linked items can still be updated, which preserves some operational flexibility without allowing the signed content itself to drift.
The same page also keeps a signature audit trail, which makes it easier to review who was invited, who signed, and what happened afterward.
