This page shows how to apply tags to Unity Catalog securable objects.
Tags are attributes that include keys and optional values that you can use to organize and categorize securable objects in Unity Catalog. Using tags also simplifies the search and discovery of tables and views using the workspace search functionality.
warning
Tag data is stored as plain text and may be replicated globally. Do not use tag names, values, or descriptors that could compromise the security of your resources. For example, do not use tag names, values or descriptors that contain personal or sensitive information.
Supported securable objectsâSecurable object tagging is currently supported on catalogs, schemas, tables, table columns, volumes, views, registered models, and model versions. For more information about securable objects, see Securable objects in Unity Catalog.
Beta
This feature is in Beta.
Governed tags are tags that are managed and enforced by a tag policy. Tag policies allow admins to define which tag keys are governed, specify the allowed values for those tags, and control who can assign or modify them. This provides organizations with centralized control over tag usage, supporting consistent data classification, compliance, and operational standards.
When a tag is governed by a tag policy:
Only users or groups with the appropriate permissions can assign or modify the governed tag.
Only the allowed values specified in the tag policy can be used for that tag key.
A lock is displayed next to the tag.
If a tag policy is deleted, any tags that were previously governed by that policy become ungoverned. The tags themselves are not removed from objects, but anyone can assign or modify tags with the same name without requiring special permissions.
Governed tags help ensure that important metadata, such as data classification, regulatory status, or cost center, is applied consistently and according to your organizationâs governance requirements. All users with appropriate privileges can create and assign tags that are not governed by tag policies. Tag policies only apply to tags that are explicitly governed.
For more information, see Tag policies.
note
If you are enrolled in the dashboard tags Private Preview, any tag assigned to a dashboard that matches the name of a governed tag is automatically subject to that tagâs policy.
System tagsâSystem tags are a special type of governed tag that are predefined by Databricks and enforced by tag policies. System tags have a few distinct characteristics:
System tag definitions (keys and values) are predefined by Databricks.
Users cannot modify or delete system tag keys or values.
Users can control who is allowed to assign or unassign system tags through tag policy permission settings.
A wrench is displayed next to the tag.
System tags are designed to support standardized tagging across organizations, particularly for use cases like data classification, ownership, or lifecycle tracking. By using predefined, governed tag definitions, system tags help enforce consistency without requiring users to manually define or manage tag structures.
RequirementsâTo add tags to Unity Catalog securable objects, you must own the object or have all of the following privileges:
APPLY TAG on the objectUSE SCHEMA on the object's parent schemaUSE CATALOG on the object's parent catalogTo add a governed tag to Unity Catalog securable objects, you must also have the ASSIGN permission on the tag policy. See Manage tag policy permissions.
ConstraintsâThe following is a list of tag constraints:
Tag keys are case sensitive. For example, Sales and sales are two distinct tags.
You can assign a maximum of 50 tags to a single securable object.
The maximum length of a tag key is 255 characters.
The maximum length of a tag value is 1000 characters.
The following characters are not allowed in tag keys:
. , - = / :
Trailing and leading spaces are not allowed in tag keys or values.
Tag search using the workspace search UI is supported only for tables and views.
Tag search requires exact term matching.
To add and update securable object tags using Catalog Explorer:
Click Catalog in the sidebar.
Select a securable object.
On the object Overview page, add or update a tag:
You can use the Add/Edit tags dialog to add and delete multiple tags.
Tag keys are required. Tag values are optional.
To add or delete table column tags, click the Add tag icon.
note
This feature is available in Databricks Runtime versions 13.3 and above.
You can use the ALTER <object> SQL command to tag catalogs, schemas, tables (including views, materialized views, streaming tables), volumes, and table columns. For example, you can use the SET TAGS and UNSET TAGS clauses with ALTER TABLE to manage tags on a table. See DDL statements for a list of available Data Definition Language (DDL) commands and their syntax.
For registered models, you must use Catalog Explorer or the MLflow ClientAPI. See Use tags on models.
Use the Databricks workspace search bar to search for tables and views using tag keys and tag values. You can use both table tags to search. You cannot use tags to search for other tagged objects, like table columns, catalogs, schemas, or volumes.
Only tables and views that you have permission to see appear in search results. This means that you must have at least the BROWSE privilege on the object (or on the object's parent catalog and schema) to return the object in search results.
For details, see Use tags to search for tables.
Retrieve tag information from information schema tablesâEach catalog created in Unity Catalog includes an INFORMATION_SCHEMA. This schema includes tables that describe the objects known to the schema's catalog. You must have the appropriate privileges to view the schema information.
You can query the following to retrieve tag information:
For more information, see Information schema.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4