How to Create a Managed Metadata Column in SharePoint
Managed Metadata is your tenant-wide vocabulary. Use it when terms must be consistent across every site, library, and team in the organisation.
What it is
Managed Metadata columns connect to the Term Store — a centrally-managed taxonomy maintained by your SharePoint admins. Departments, document types, locations, product lines, project codes — anything that should mean the same thing across the entire organisation lives in the Term Store, and any library can have a Managed Metadata column that pulls from it.
The advantage over Choice columns is enormous when you operate at scale. With Choice, every library has its own list of departments — and every list drifts. Some libraries say ‘HR’; others say ‘Human Resources’. Reports across libraries become impossible. With Managed Metadata, every library uses the same source. Update the term in one place and every library that references it updates automatically.
The Term Store also supports synonyms (typing ‘HR’ tags as ‘Human Resources’), translations (different languages), and hierarchies (parent-child relationships, e.g. ‘Australia’ under ‘APAC’). For any organisation managing content at scale, Managed Metadata is the foundation of consistent classification — and the foundation of accurate Copilot search.
The ‘AI ready’ difference
Copilot is far more accurate when content is tagged with consistent, structured metadata. A library where every file has ‘Department: HR’ (from a managed term set) gives Copilot reliable signals. A library where files have ‘HR’ and ‘Human Resources’ and ‘human-resources’ as text tags gives Copilot mush. Managed Metadata isn’t optional for serious AI readiness — it’s foundational.
When to use this
- For tenant-wide terms: Departments, Document Types, Locations, Product Lines.
- When the same vocabulary needs to appear in many sites and libraries.
- When you want central governance of categories — not library owners inventing their own.
- When you’re preparing for Copilot and need consistent, structured tags.
How to do it
- Have your admin set up the term group and term set in the Term Store first (see M-14).
- In your library, click + Add column → Managed Metadata.
- Select the relevant term set.
- Decide: multiple values allowed? Display the entire path? Allow fill-in?
- Save and start tagging files.
- Users get type-ahead suggestions from the term set.
Best practices
- Reserve Managed Metadata for genuinely tenant-wide terms. Don’t put every list in the Term Store.
- Plan governance before rolling out. Who owns each term set? Who can add new terms? Document this.
- Use synonyms for natural language. If everyone says ‘HR’ but the official term is ‘Human Resources’, a synonym lets both work.
- Combine with Choice columns where appropriate. Tenant-wide terms = Managed Metadata. Library-specific lists = Choice.
Common mistakes
- Putting everything in the Term Store. Some lists belong locally as Choice columns. Don’t over-centralise.
- No governance. If anyone can add terms, the taxonomy drifts and quality crumbles.
- Allowing fill-in values without a plan. Defeats the consistency purpose. Use sparingly with monitoring.
The File Sanity Kit gives you the Container Method™ — audit, restructure, and future-proof SharePoint without IT admin. The complete methodology, full workbook, and 8-tab Excel planner.
Get the File Sanity Kit — $27 →FAQ
What is a Managed Metadata column in SharePoint?
A Managed Metadata column draws values from the Term Store — a tenant-wide library of terms managed by your SharePoint administrators. Unlike Choice columns (library-scoped) or Lookup columns (site-scoped), Managed Metadata applies across the whole tenant. Define ‘Department’ once in the Term Store, use it in 50 libraries across 20 sites, all referencing the same authoritative values.
What’s the difference between Managed Metadata and Choice?
Scope. Choice is library-scoped — each library has its own list, maintained by the library owner. Managed Metadata is tenant-scoped — terms live centrally in the Term Store and apply everywhere. Use Choice for process-specific tags (Status, Phase, Priority). Use Managed Metadata for organisational attributes (Department, Document Type, Location).
Can Managed Metadata columns have hierarchies?
Yes — that’s one of the main reasons to use them. Terms can have parent/child relationships (Operations → Logistics → Warehousing), and users can pick at any level. SharePoint understands the hierarchy when filtering and reporting, so filtering by ‘Operations’ returns items tagged with ‘Logistics’ or ‘Warehousing’ too. Choice columns are flat by comparison.
Who can create Managed Metadata terms?
By default only Term Store administrators can create or edit terms. You can assign Term Set owners and contributors for specific term sets, allowing them to manage just their slice without admin rights. Whatever you do, don’t enable ‘Allow fill-in’ on Managed Metadata columns by default — it lets every user add terms and defeats the whole governance model.