Skip to main content
Tags are how documents get grouped across folders. You apply them on a document, and you curate the set of tags your workspace uses on the Tags page.

Applying tags to a document

Open a document and find the Tags card in the properties rail. Type into the Add tag input and press Enter, or click away, to add. Each tag chip has its own remove button. Whatever you type becomes a tag. There is no picker, no autocomplete, and no check against the registry here, so a typo just becomes a new tag.
A document can carry at most five tags. Nothing in the editor stops you adding a sixth. The save fails instead, and the save indicator shows Failed to save without saying why.

The Tags page

Click Tags in the sidebar to open the tag registry. When tags are in use that you have not yet registered, the sidebar row carries a badge with how many are waiting. The page opens with a filter input that narrows every section at once.

The three tiers

Registered tags are grouped into three tiers. They are independent, not a hierarchy: a Topic does not belong to an Area, and a Goal does not belong to either. The page states the convention as: every document carries one Area, up to two Topics, and up to two Goals. A pricing page spec, for instance, might be Area product, Topic pricing, Goal acquisition.
Those per-tier counts are guidance, not rules. Nothing checks them. You can tag a document with three Areas and no Goal and it will save. The only enforced limit is five tags per document.

Creating a tag

Click New tag to open an inline form: a name, a tier (Area, Topic, or Goal), and an optional description. Names must be kebab-case: lowercase letters, numbers, and single hyphens, up to 64 characters. Anything else is rejected inline with Lowercase letters, numbers, hyphens only.

The registry table

Each tier lists its tags in a table with columns Tag, Description, Docs, and an actions column. Docs is a live count of how many documents currently carry that tag. The actions menu on each row offers:
  • Rename: prompts for the new name in a browser dialog. The same kebab-case rule applies.
  • Edit description: edits in place. Enter or clicking away saves, Escape reverts.
  • Change tier: move the tag to Area, Topic, or Goal. The tier it is already in is disabled.
  • Delete: removes the entry from the registry after a browser confirmation.
Deleting a registry entry does not untag anything. The confirmation says so directly: documents keep the tag, it just drops out of the tiered structure. Because those documents still carry it, the tag reappears in the review queue below.

The review queue

Below the registry is a section headed Needs review (n) — used on documents, not yet in your registry. It collects every tag that exists on a document but has no registry entry, which is how typos and ad-hoc tags surface. When there is nothing outstanding it reads All tags reviewed. Each row shows the tag, how many documents carry it, and two dropdowns.

Add to registry

Pick As area, As topic, or As goal. The tag gets a registry entry in that tier and leaves the queue. Nothing about the tagged documents changes, since they already carry the tag.

Merge into

Pick any registered tag to fold this one into it. A browser confirmation spells out what happens: documents tagged with the loose tag will be retagged to the target.
Merge and delete do different things. Merge retags your documents: after merging pricing-page into pricing, those documents carry pricing. Delete only removes the registry entry and does not touch documents at all.
If you have not registered any tags yet, the merge dropdown shows No registered tags yet, since there is nothing to merge into.