Organize codes with tags

Use tags to describe themes that cross folders, such as a campaign, location or responsible team. Open Folders & tags to create a tag, or enter tag names in an asset's Organization section. Tags describe resources; they do not grant access.

When editing an asset, separate tag names with commas and save organization. Use short, consistent names and avoid empty values. An asset accepts at most 30 tags, and individual tag names must respect the service's length rules. Duplicate names are normalized rather than creating extra access rights.

Reopen the asset and inspect the stored tags. Check that the destination and public link remain unchanged. Agree on naming with your team before tagging a large campaign so slightly different spellings do not become confusing labels.

If saving reports an invalid tag or another-workspace error, correct the input instead of trying another asset. A read-only Analyst cannot change organization. Removing a label is not the same as deleting an asset or transferring its ownership.