Documents

Write and store Markdown documents, link them to clients or projects, tag them, and export them to PDF — with every change archived automatically.

Documents are Markdown notes you can store, link to any number of clients and projects, tag, and export as a PDF. Every time you change the content, the previous version is archived automatically so you can look back or restore it — see Document versioning.

What you can do

Browse all your documents on the Documents page with text search and tag filters, and create a new document at any time. Open a document to read its full content, then use the actions there to edit it, view its version history, export it to PDF, or delete it.

Each document gets an ID like D-7. You can change the letter prefix in General settings.

Fields you fill in

  • Name — required, the document title.
  • Content — required Markdown text.
  • Description — optional summary, shown above the content on the detail page.
  • Clients — optional links; the document then appears in each linked client's related documents.
  • Projects — optional links; the document appears in each linked project's related documents.
  • Tags — optional, shared with the rest of Tags.

Writing in the editor

The editor has two modes: a WYSIWYG rich-text editor (the default) and a raw Markdown textarea. Switch between them with the toggle in the editor toolbar — write visually, or drop down to the Markdown source when you need it. Either way the content is stored as Markdown. There are no slash commands, embedded media, or image uploads. Content is required; everything else is optional.

The list

The documents list shows the ID, name (with the description as a subtitle), clients, projects, tags, and the last-updated date. The clients and projects columns list every linked entity as clickable links, with a "+N" overflow when there are more than fit. You can search across name, description, and content, and filter by tags (a document must carry all the tags you pick). Choose 50, 100, or 200 documents per page.

The list doesn't offer client or project filters directly — to see a particular client's or project's documents, open that client or project and use its related-documents list.

The detail page

A document's detail page shows the title, description, all linked clients and projects as clickable names, tags, the last-updated time, and the full content. A PDF exports section lists any PDFs you've generated. From here you can Edit, view History, Delete, or Close.

Workflows

Create a document

  1. Open the new document form.
  2. Enter a name and write the content as Markdown.
  3. Optionally link one or more clients and projects, and add tags.
  4. Save. The document gets the next ID.

Update a document

Use Edit, make your changes, and save. If the content actually changed, the previous version is archived before the new content takes its place. Editing only the name, description, clients, projects, or tags does not create a new version.

Export to PDF

Use the Export PDF action on the detail page. Each export captures the document exactly as it was at that moment — name, content, tags, and linked clients/projects — so later edits never change a past export. The exports section lists each PDF with its size and date; download or delete them individually. The PDF contains the document text as it was when generated; it doesn't include any version history.

How it connects to the rest of Ceum

  • Clients and projects — a document links to any number of clients and projects (all optional). It shows up in each linked client's and project's related documents. If you delete one of those clients or projects, the document stays — it just loses that one link.
  • Tags — shared with the tagging system across Ceum.
  • History — document edits are tracked through version snapshots, not the general Entity changelog; see Document versioning.

Tips and edge cases

  • Deletion is permanent. Removing a document also removes its version history and exported PDFs — there's no trash bin.
  • Documents are stored as Markdown. You can edit them visually in the rich-text mode or in raw Markdown, but there's no embedded media and no separate image uploads.
  • Versioning runs only on content changes. Renaming, retagging, or relinking a document doesn't create a version snapshot.
  • No field-level change log. For documents, the version timeline is the history surface — there's no who-changed-what audit trail.

On mobile

  • Create and edit documents in a native bottom-sheet form; edits made offline are queued and sent on reconnect — see Offline support.
  • You can read a document and export it to PDF (shared through the native share sheet), but version history and restore are web-only.

Open in app

Related articles