Working with Tags

Intermediate

How to use tags to categorize and label your model elements for easy filtering and organization.

Tags are lightweight labels you can attach to any model element for categorization and filtering.

Adding Tags to an Element

  1. Select a node or relationship (on the canvas or in the Model Navigator)
  2. In the Properties Panel, find the Tags section
  3. Type a tag name and press Enter to add it
  4. Add as many tags as needed

Removing Tags

  1. Select the element
  2. In the Tags section, click the × on the tag you want to remove

Filtering by Tags

Tags become powerful when combined with filters:

  1. Open the Filters area in the Model Navigator
  2. Set a filter condition for a specific tag
  3. The Model Navigator shows only elements with that tag

Tags beyond nodes and relationships

Tags aren't limited to nodes and relationships. Almost anything you can select has a Tags section in its Properties Panel — diagrams, grid views, folders, saved filters, navigation trees, renderings, publications, assets, and the simulation elements (twins, scenarios, agents, dashboards). The one exception is the connections between agents in a simulation, which carry no tags.

Tags and the AI assistant

You can ask the AI assistant to tag things for you — "tag every deprecated service with needs-review" — and it can read tags back when you ask it to find something. External tools connected over MCP can do the same, and they see the same full range of element kinds.

One thing worth knowing: setting tags replaces whatever was there. If you ask the assistant to add a tag, it reads the existing ones first and sends them back with the new one. If you're scripting this yourself, do the same — otherwise you'll wipe the tags already on the element.

Tag Ideas

  • Status: "in-progress", "approved", "deprecated"
  • Priority: "critical", "nice-to-have"
  • Domain: "infrastructure", "security", "frontend"
  • Review: "needs-review", "reviewed"

Tips

  • Tags are free-form text — there's no predefined list
  • Use consistent naming conventions across your team
  • Capitalization is ignored, so "Security" and "security" are the same tag
  • Tags complement properties — use properties for structured data, tags for flexible categorization
← Previous

API Tokens and External Access

Next →

Styling Nodes (Shapes, Colors, Borders)

This content was written collaboratively with AI.