Tag
A Tag in Salesforce is a user-defined keyword or short phrase that you attach to a record to categorize it and find it again later through tag-based search.
Definition
A Tag in Salesforce is a user-defined keyword or short phrase that you attach to a record to categorize it and find it again later through tag-based search. There are two kinds. Personal Tags are private to the user who applied them, and Public Tags are visible to everyone in the org once an admin turns the feature on.
How tagging actually works in Salesforce
A free-text label, not a picklist
The whole point of a Tag is that nobody pre-defines the allowed values. A user types whatever word or short phrase fits, and Salesforce attaches it to the record. That freedom is the feature and the weakness at the same time. You can tag a handful of Accounts with "Q3-followup" in seconds, without an admin building a custom field or picklist first. Nothing stops a teammate from typing "Q3 follow up" or "q3-follow-up" on the next record, so the same intent ends up under three different labels. Because the values are not controlled, tags are great for quick, throwaway organization and weak for anything you plan to report on. A picklist or custom field gives you clean, reportable data. A tag gives you a sticky note. Salesforce treats tags as a personal productivity aid layered on top of your existing data model, not a replacement for proper fields. Knowing that distinction up front saves you from trying to run pipeline analytics off something that was only ever meant to help one person find a record again.
Personal tags versus public tags
The two tag types differ in who can see them and who can clean them up. Personal Tags are private. You see only the personal tags you created, and another user looking at the same record never sees them. They are perfect for a private "read later" list or for marking the deals you personally care about this week. Public Tags work differently. Once an admin enables them, any public tag a user applies is visible to everyone in the org, which turns tagging into a shared vocabulary the whole team can search against. Permissions follow the same split. You can rename or delete any of your own personal tags freely. Renaming or deleting a public tag requires the Tag Manager permission, because that change affects what every other user sees. Public Tags is not on by default in every org. In some editions an admin submits an activation request to Salesforce before the option even appears under Tag Settings. Plan which type you want before rolling tagging out, because the two behave quite differently in practice.
Finding records through the Tags page
Tagging only pays off if search is easy, so Salesforce Classic gives tags their own browsing surface. You reach the Tags page by clicking any tag name on a record detail page, or by selecting Tags in the sidebar if your admin added that component. From there you can list tags alphabetically or sort them by how often or how recently they are used, which surfaces the labels you actually rely on. A Search Tags box lets you type a string of at least two characters, and it accepts wildcards and operators for more precise matches. The useful trick is selecting more than one tag at once. When you pick multiple tags, Salesforce returns only the records that carry all of them, so "VIP" plus "renewal" narrows straight to your high-value renewals. Public tags appear to everyone who searches, while personal tags appear only to the person who created them. This tag-driven view sits alongside list views and global search rather than replacing them, giving you a fast, theme-based way to regroup records that span several objects.
Limits you will hit at scale
Tags carry hard caps, and they are lower than people expect, which is part of why the feature suits light use rather than heavy data management. Each user can create up to 500 unique personal tags. Each user can also apply personal tags to records up to 5,000 times, counting every instance rather than every distinct label. So one personal tag stuck on 5,000 records would exhaust that whole allowance on its own. At the org level, Salesforce allows up to 5,000,000 personal and public tags applied to records across every user combined. That ceiling sounds huge, but a large org with enthusiastic taggers can creep toward it over years. When you approach the limit, cleanup matters. Admins can delete the personal tags belonging to deactivated users to reclaim room, and the Tag Manager permission lets the right people prune stale public tags. These numbers are worth knowing before you encourage a team to tag everything, because the limits are a clear signal that Salesforce designed tags for selective, personal use and not as a substitute for structured fields and reports.
Why tagging is a Classic-era feature
The tags interface described here lives in Salesforce Classic. The Tags page, the sidebar component, and the Tag Manager permission are all Classic features, and the classic tagging UI did not carry over to Lightning Experience in the same form. That single fact explains why tagging feels like a legacy capability today. Most orgs now run on Lightning Experience, where the day-to-day workflows that tags once handled are covered by other tools. List views filter and group records on demand. Reports and dashboards turn structured fields into real analytics. Topics add a shared, searchable vocabulary across records and Chatter. For purely personal organization, Salesforce introduced Personal Labels in Lightning, which lets a user privately label and quickly find their own records without an admin building anything. Tags still exist and still work, so orgs that lean on Classic, or that built habits around public tags years ago, can keep using them. But for a new implementation on Lightning, you would reach for list views, reports, topics, or Personal Labels first, and treat tags as the older approach you inherited rather than the one you would choose fresh.
Turning tags on and rolling them out
Tagging is off until an admin enables it, and the switch lives under Setup. You search Tag Settings in the Quick Find box, then choose which tag types to allow and add the tag section to the relevant page layouts so users can actually apply tags on records. Personal Tags are the simpler half to enable. Public Tags can require an activation request to Salesforce first in some editions, and only after activation does the Enable Public Tags option show up under Tag Settings. Tags are available in most editions, with Database.com being the notable exception. A sensible rollout starts small. Decide whether you genuinely need shared public tags or whether private personal tags solve the problem, since public tags create a shared namespace that needs light governance to stay tidy. Add the Tag Manager permission only to the handful of admins or power users who should rename and delete public tags. Communicate a simple naming convention up front, because once free-text labels multiply across hundreds of records, untangling near-duplicates by hand is tedious. Keep the limits in view and you can let tags do the lightweight job they are good at.
Enable and configure Tags in Salesforce
Tagging is disabled until an admin enables it under Setup. Here is how to turn on Personal and Public Tags and make them usable on records in Salesforce Classic.
- Open Tag Settings
From Setup, type Tag Settings in the Quick Find box and select Tag Settings. This is where you control which tag types your org allows.
- Enable the tag types you want
Turn on Personal Tags for private labeling. To allow Public Tags, enable that option too. If the Public Tags option is missing, it has not been activated for your org and you submit an activation request to Salesforce first.
- Add tags to page layouts
Choose which objects show a tag section, so users can apply tags directly on Account, Contact, Opportunity, and other record detail pages.
- Grant Tag Manager where needed
Assign the Tag Manager permission to the small group of admins or power users who should be able to rename and delete public tags across the org.
Private labels visible only to the user who created them. Each user gets up to 500 unique personal tags and 5,000 applied instances.
Labels visible to the whole org, creating a shared searchable vocabulary. May need a Salesforce activation request before the option appears.
Required to rename or delete any public tag. Personal tags can always be renamed or deleted by their own creator without it.
An optional Classic sidebar link that opens the Tags page for browsing and searching tags by name, frequency, or recency.
- The classic tagging UI is a Salesforce Classic feature and did not carry into Lightning Experience in the same form. On Lightning, consider Personal Labels, list views, reports, or topics instead.
- Tags are free text with no validation, so near-duplicates like "follow up" and "follow-up" pile up fast. Agree on a naming convention before a team starts tagging.
- Public Tags is not on by default in every edition and can require an activation request to Salesforce before it appears under Tag Settings.
- Tags are unreliable for reporting because the values are not controlled. Use a picklist or custom field when you need clean, reportable data.
Trust & references
Cross-checked against the following references.
- Topics and Tags SettingsSalesforce
- Find Records Using Salesforce Classic TagsSalesforce
Straight from the source - Salesforce's reference material on Tag.
- Enable TagsSalesforce
- Organize and Find Records Easily with Personal LabelsSalesforce
Hands-on resources to go deeper on Tag.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Tag?
Q2. What types exist?
Q3. How do they complement other features?
Discussion
Loading discussion…