SharePoint taxonomy is a controlled hierarchy of terms used to classify content consistently. In SharePoint Online, the Term Store holds reusable term sets that managed metadata columns can present to authors.
Do not begin by drawing a huge hierarchy. Begin with one retrieval problem, a named owner and a small vocabulary that users can apply reliably.
Know the main objects
Microsoft's managed metadata introduction defines the important pieces:
- a term is a word or phrase used for classification
- a term set is a related group of terms
- a term group contains term sets and provides an administrative boundary
- a managed metadata column lets a list or library use terms
- a global term set can be reused across sites
- a local term set is available within its site collection
An open term set allows contributors to add terms during tagging. A closed term set limits users to approved choices. Use open sets only where that flexibility has an owner and review process.
Start with a retrieval question
Suppose people need to find policies by Department and Policy type.
Interview content owners and searchers. Collect the terms already used, including synonyms and ambiguous labels. Decide which concept needs hierarchy and which is better as a flat choice field.
Do not encode every organisational detail. A taxonomy should make retrieval more consistent, not reproduce an organisation chart in miniature.
Assign governance before configuration
The Term Store has specific roles. A Term Store Administrator can manage the store and administrative roles. Group Managers and Contributors work within assigned term groups.
The Owner, Contact and Stakeholder labels on a term set are useful governance information but do not grant administrative permissions. Microsoft makes that distinction in its Term Store role guidance.
Record the business owner, administrator, group manager, people allowed to propose changes, review frequency and retirement policy.
Configure and test a small term set
An administrator can open the Term Store from the SharePoint admin centre. Create a term group, assign managers or contributors, then create the term set and terms.
Use labels people recognise, add useful synonyms, provide guidance for ambiguous terms, avoid unnecessary depth and decide whether the set is open or closed.
Create a managed metadata column in a test library and connect it to the term set. Decide whether one or multiple values are allowed. Multiple values can complicate views, integrations and reporting.
Test with representative documents and ordinary contributors. Check authoring, synonyms, required fields, filters and search. Test flows and reports with the field's actual data shape.
Manage change deliberately
Prefer supported deprecation or merge behaviour over deleting a term without understanding existing tags.
Keep a change record with the reason, approver and affected integrations. Communicate changes and retest important views, search queries and flows.
Managed metadata can improve consistency. It cannot compensate for missing ownership, weak content or permissions, and it does not prove that search or Copilot will answer a question correctly.
For a practical review of your taxonomy, libraries and ownership model, join the SharePoint & Teams Admins Space.