Skip to content

Classify content with tags

Tags provide cross-cutting classification independent of the map hierarchy. Use them to categorize topics by feature area, user role, content type, or any dimension useful for filtering and organizing.

Create tag groups

  1. Go to Tags in the sidebar.

  2. Click New Group and name it — e.g., "Feature Area" or "User Role."

  3. Choose a color for the group.

Add tags to a group

  1. Open a tag group.

  2. Click Add Tag and enter a name — e.g., "Authentication," "Billing," "Admin-only."

  3. Add tags within each group.

Tag a topic

  1. Open a topic in the editor.

  2. Below the title, find the tag picker.

  3. Click to toggle tags on and off. Selected tags appear as colored pills.

Define your tag groups before you start tagging. Establishing a consistent taxonomy upfront (e.g., one group for feature areas, one for content types, one for user roles) prevents ad hoc tags that overlap or conflict as your project grows.

Tag use cases

Tag group

Example tags

Purpose

Feature area

Authentication, Billing, Reporting, Integrations

Filter topics by product area for targeted reviews

Content type

Concept, Procedure, Reference, Troubleshooting

Identify what kind of content each topic contains

User role

Admin, End user, Developer, Partner

Track which audiences each topic serves

Status

Draft, Needs review, Approved, Deprecated

Manage editorial workflow across the team

Platform

Web, iOS, Android, Desktop

Flag platform-specific content for audits

How tags differ from conditions

  • Tags are metadata for organizing and filtering within the project. They don't affect what gets published.

  • Conditions control content visibility — conditional blocks are included or excluded at publish time.

Use tags when you want to categorize content for your authoring team. Use conditions when different audiences should see different content.

Tags are an authoring-side tool only. They are never visible to readers and have no effect on published output. If you need to show or hide content based on audience or product variant, use conditions instead.


See also

Was this page helpful?