How to Add a Department or Function Column in SharePoint
Department tells SharePoint which part of the business owns or relates to the content. It’s the second-most-important metadata column after Document Type.
What it is
A Department (or Function) column captures which business unit a document belongs to — Finance, HR, Marketing, Operations, IT, Legal, Sales. Combined with Document Type, it answers most of the routing and ownership questions a library has to handle. ‘Show me all HR policies’, ‘show me all Finance contracts’, ‘who owns the IT procedures’ — all become one-click queries.
The right place for Department in most organisations is in the Term Store as Managed Metadata. Departments are a tenant-wide concept that should mean the same thing everywhere. Marketing is Marketing whether you’re tagging a contract, a meeting minute, or a budget — and changes (mergers, renames, splits) happen centrally instead of in every library independently.
The column also has governance implications. When a department restructures, the Term Store can be updated centrally, and every file tagged with that department updates automatically. When someone leaves a department, you can audit which files were owned by that department and reassign appropriately. This kind of structural management is what scales SharePoint to enterprise size.
When to use this
- On every library that holds content from or about specific business units.
- When ownership crosses team boundaries and you need to track it.
- For department-specific reporting and filtering.
- When you want to align library access with organisational structure.
How to do it
- Confirm the official list of departments (often from HR or your org chart).
- Add as Managed Metadata in the Term Store (preferred) or Choice (for single-site use).
- Add the column to the library: + Add column → choose your type.
- Set values to match the official department list.
- Make required if every file should be classified.
- Set a default if 90% of files belong to one department.
- Use to filter and create department-specific views and Power Automate flows.
Best practices
- Use Managed Metadata for cross-tenant consistency. Departments shouldn’t drift between libraries.
- Match to your HR org structure. If HR says it’s ‘People & Culture’, so should SharePoint.
- Update when the org changes. Mergers, splits, renames — keep the Term Store current.
- Combine with Document Type. Together they answer ‘what is this and who does it belong to?’ for almost every file.
Common mistakes
- Different department lists in different libraries. Cross-library reporting becomes impossible.
- Stale lists after org changes. Six-month-old department names confuse users and break process.
- No Department column at all. Half your filtering needs become unanswerable.
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 Department column in SharePoint?
A Department (or Function) column tags every file with the business unit it belongs to: HR, Finance, Marketing, Operations, IT. It’s the organisational counterpart to Document Type. Where Document Type answers ‘what is this?’, Department answers ‘whose is this?’. Together, the two columns cover most of what you need to find content across a complex environment.
Should Department be a Choice column or Managed Metadata?
Managed Metadata, almost always. Departments are tenant-wide concepts — every library across the organisation should reference the same list. If HR is tagged ‘HR’ in one library and ‘Human Resources’ in another, you’ve got exactly the inconsistency the Term Store was designed to fix. Build the department term set once, use it everywhere.
What if our organisation restructures? Will the Department column break?
With Managed Metadata, restructures are manageable but require care. Renaming a department in the Term Store propagates to every reference automatically. Merging two departments needs the term to be merged in the Term Store (SharePoint moves the references). Deleting a department clears all tagged items — usually you want to retire and replace, not delete. Plan the change before executing in production.
Can a file belong to multiple departments in SharePoint?
Yes — make the Department column multi-value. Useful for cross-functional content (e.g. an HR + Legal policy on workplace conduct). The trade-off: filtering by Department then returns items where the chosen department is one of several — which is usually what you want, but worth understanding. For most ownership-style use cases, single-value is cleaner.