Skip to content

Tags

Tags are flat labels (no nesting) you attach to documents to organize and find content across collections. A document can carry any number of tags.

Add or remove tags on a document from the document’s tag control. Typing a new name creates the tag (reused by name within the team); existing tags autocomplete. Tags are normalized to lowercase for matching, so Funktion and funktion are the same tag.

Tags also sync with the Obsidian plugin (the note’s tags: frontmatter) and the REST API (tags: string[]).

Settings → Tags lists the team’s tags with usage counts, where you can rename, recolor, or delete them. You can favorite (pin) tags you use often so they surface first in pickers and the sidebar.

Use tags to filter the document list / sidebar and to scope publishing channels (publish only documents carrying a given tag).

On the /search page you can stack multiple tags with AND semantics — only documents carrying all the selected tags match. Add a tag in the filter panel, remove one via its chip; the state lives in the URL as repeated ?tag= parameters and works the same over the REST API. This makes tags a simple query language: tag a page once with every category it belongs to, then intersect (A and B) with one filter instead of building combined collections.

A tag can be made restricted by attaching an access-control list — only granted users/groups can see and apply it. Restricted tags are useful for sensitive classifications (e.g. an internal codename).