Setting up Topics is a three-layer configuration: enable the feature on the right objects, write a starter list of canonical Topics, and assign Topic Moderators with the Modify Topics permission. The platform handles record creation and the TopicAssignment junction automatically, so the work is less about wiring things up and more about deciding which objects to enable, what the canonical Topic list looks like, and who maintains it. Skip the third step and the Topic list fills with one-off variants within a quarter.
- Enable Topics for the right objects
Open Setup, search Topics for Objects, and check the boxes for objects where Topics will add value. Common picks are Account, Contact, Lead, Opportunity, Case, Knowledge Article, and Files. Resist the temptation to enable Topics on every object. Each enabled object adds a Topics field to the detail page and a small amount of cognitive load for users. Save the change and test the field appears on a sample record. If Lightning page layouts have been customized, you may also need to add the Topics component to the record page through App Builder.
- Write a starter list of canonical Topics
Pick 20 to 50 Topics that the org cares about and create them up front rather than letting them emerge organically. Common categories are product lines (one Topic per product), customer segments (Enterprise, Mid-Market, SMB), regions (North America, EMEA, APAC), and project codes (one Topic per major initiative). Add a description to each Topic so users understand which one to pick. Publish the list in a place every employee can find. Refresh it quarterly to retire stale entries and add Topics for new initiatives, since the alternative is the list growing by user-typed variants.
- Assign Topic Moderators and write a merge SLA
Designate three to five users as Topic Moderators by granting the Modify Topics permission through a permission set. Their job is to merge spelling variants of the same Topic into a canonical record, retire Topics with no recent activity, and hide off-topic or spam Topics from search results. Write a one-line SLA for the team, such as merge variants within one business day so the related-topic graph does not get polluted. Track the moderation queue in a Chatter group or a simple custom list view so handovers between moderators stay clean and visible.
- Add the Topics component to high-traffic Lightning pages
Use Lightning App Builder to add the Topics component to the record pages where Topics matter (Account, Opportunity, Case, Knowledge Article). The component shows the Topics applied to the current record and lets users add or remove Topics inline. On the home page, add a Topic Trends card so users see which Topics are gaining activity. On the global search results page, configure Topic-aware filters so a user searching for a Topic name sees both Topic records and records tagged with that Topic, not just keyword matches.
- Disabling Topics on an object hides the field but does not delete the TopicAssignment records. They resurface if the feature is re-enabled. Plan a deletion pass if you truly want them gone.
- Topics are case-insensitive but display-case-sensitive. A Topic created as Q4Results displays as Q4Results, but a lowercase hashtag in a post attaches to the same Topic. Pick a casing convention and stick to it.
- Spelling variants count as different Topics until a moderator merges them. Without a merge SLA, the Topic list grows to thousands of entries within a year, most of them near-duplicates.
- The related-topic graph rebuilds over time. A newly created Topic needs a few days of activity before it shows up in recommendations, so do not expect instant suggestions on fresh Topics.
- Topics, Tags, and Categories solve different problems and are not interchangeable. Standardize new work on Topics; keep Categories for Knowledge data category visibility; retire Tags from new processes.