Tags: One Catalog Across Contacts, Companies, Documents and Photos
How one tag catalog serves four record types without turning every list into a sticker collection.
The universal tag system gives contacts, companies, documents and photos one shared catalog. A “GDPR” tag has one definition and one scope model whether it appears on a company, a contact, a document or a photo of a cracked lid. /settings/tags is the catalog manager; the old contact-tag address at /settings/core/contact-tags redirects there.
The catalog
Each tag has a name, a category it is grouped under, a scope — any combination of contact, company, document and photo — and an active flag. The page shows system tags and custom tags grouped per category, searchable and browsable. A tag can be company-only (“Strategic Partner”), document-only (“Master Service Agreement”) or universal (“GDPR-relevant”). The scope decides where the tag appears in the tag pickers on a record, so a photo picker is not cluttered with tags that only make sense on a contract.
System and custom
System tags come with the platform and are managed as a fixed set. Custom tags are the tenant’s own: your team creates them, picks their scope, deactivates them when they stop being useful and deletes them when they were a mistake. Deactivating is the polite option — the tag stops being offered on new records while everything already tagged keeps its meaning. Tags render in one neutral style, deliberately. There is no color picker, so nobody has to decide whether urgent is red, salmon or a slightly aggressive pink. Meaning lives in the name and the scope. Not in the hue.
What makes a good tag
Tags are best for short, reusable labels. If a tag needs a sentence to explain what it means, it is probably a note, not a tag. Check the category list before creating a near-duplicate — “GDPR-relevant” and “GDPR Relevant” are two rows, and two rows are two filters, two reports and one argument. Since there is no merge, the cheapest fix is the search box before the create button.
Other taxonomy pages
Tags aren’t the only taxonomy. /settings/industries holds company industries, /settings/contact-roles the roles a contact has within a company, /settings/services the service catalog and /settings/core/categories the device categories. Each is its own catalog scoped to its own domain, and each follows the same idea: a structured row you can filter on beats a free-text field you can only regret.