Skip to main content
Tags let you standardize how your organization categorizes and discovers work, so people find and reuse institutional knowledge instead of reinventing it. Tags are organized as key-value pairs in two parts. Namespaces are the allowed keys, and Tags are the allowed values within a given Namespace. Think of a Namespace as the category or dimension you classify by, and Tags as the values that category can take. You can apply tags from several namespaces to the same asset.
Three Namespaces, Methodology, Dept, and Priority, each listing its allowed tags, assigned to a Project that carries one tag chip from each.

Namespaces supply the keys and Tags the values, so one Project can carry a tag from each Namespace at once.

Building and changing the tag structure requires the CloudAdmin or Librarian role. Once it exists, anyone can apply tags to their own assets and filter by them.

​
How it works

  • Namespaces group related tags, for example business-domain, data-sensitivity, or project-status. Namespace labels are alphanumeric and accept hyphens and underscores.
  • Tags live inside a Namespace and support hierarchy through parent-child relationships. A tag is created either at the root of its Namespace or nested under an existing tag.
  • Assignment policy is set per Namespace. When Allow multiple tags per entity is off, the default, an entity holds only one tag from that Namespace at a time.
  • Supported assets are Apps, Projects, Project Templates, Datasets, NetApp Volumes, Models, Environments, and Policies. Tags appear as namespace:tag chips on the asset’s card and are searchable as soon as they are applied.

​
Apply tags

Assign and remove tags from the asset’s overview page. The asset’s owner can do this, as can SysAdmins and CloudAdmins. Tags come from the namespaces already defined in your tag structure; you don’t create tags at assignment time.
Select tags drawer on an App overview showing the tag tree and the tags selected so far

Tags are picked from the existing structure, never invented at assignment time.

What a tag attaches to depends on the asset: A Project created from a Project Template inherits every tag on that template. Tags on the template’s Datasets, NetApp Volumes, and Apps carry over to the corresponding assets in the new Project.
When a Namespace allows only one tag per entity, selecting a new tag from that Namespace replaces the tag already there.
Tags on a Model are separate from any MLflow tags on the underlying model.

​
Find tagged assets

Global search indexes tag labels and descriptions, so assets are findable by tag from Domino’s main search bar without knowing the exact Namespace or tag path. Narrow a result set to one or more tags from the filter side panel beside your results, or type the tag straight into the search bar. Each listing view for Apps, Projects, Datasets, NetApp Volumes, Models, Environments, and Policies carries its own tag filter as well. Type a Namespace name followed by a colon and the filter limits its suggestions to tags in that Namespace, which makes it fast to filter along one classification axis.
Apps and Agents listing filtered by tag, showing autocomplete suggestions for the Organism namespace

Typing a Namespace followed by a colon narrows the suggestions to that Namespace.

​
Manage the tag structure

Go to Govern > Tag Browser to build and maintain the structure. The Tag Browser shows the full tag tree alongside the assets tagged within it, with a count on each node.
Tag Browser showing the tag tree on the left and the Apps tagged with the selected tag on the right

Admins and Librarians build the structure here and see what each tag is used on.

​
Deprecate a tag

Deprecate a tag to retire a classification without breaking what already uses it. A deprecated tag stays on every entity currently assigned to it but can no longer be applied to new ones.

​
Merge tags

Merging consolidates duplicate or overlapping tags. Every assignment on the source tags transfers to the target tag, and the source tags are deleted.
Merging tags cannot be undone.

​
Import and export

Import a tag structure from CSV in the Tag Browser to migrate from a spreadsheet or an external provider. Download a sample import file to start from. The import preview flags any row with an error before anything is committed.
Each row defines one tag, and the file has no header row:
To export, use the Tags API, which returns the full tag structure as a CSV file suitable for backup or for seeding another deployment.
  • Properties: record typed, open-ended information on the same assets.
  • Knowledge management: how Tags, Properties, and search relate, and when to choose each.
  • Tags API: manage namespaces, tags, and assignments programmatically.
Last modified on August 7, 2026