SharePoint Content Types and Site Columns

Content types are reusable collections of metadata (columns), workflows, document templates, and information management policies that define a specific type of item in SharePoint. For example, a 'Contract' content type might include columns like 'Contract Value', 'Expiration Date', and 'Vendor Name', along with a retention policy and a Word template. Site columns are the individual metadata fields that can be added to one or more content types. They are defined at the site collection level and can be reused across multiple lists and libraries.

Before content types, SharePoint lists and libraries had a flat schema—every item in a list had the same set of columns. This made it impossible to store different types of items with different metadata in the same list. Content types solve this by allowing a single list or library to contain multiple item types, each with its own schema. For example, a document library can hold both 'Invoice' and 'Purchase Order' items, each with different required columns. This is critical for enterprise content management where different departments need to collaborate in the same library but track different metadata.

Content types are defined using the SharePoint Content Type Hub, a special site collection that serves as the central repository for enterprise content types. The hub is typically created at the root of the Managed Path (e.g., /sites/contenttypehub). When you publish a content type from the hub, it is made available to all subscribing site collections in the tenant. The publishing process uses the Content Type Syndication feature, which relies on a timer job called 'Content Type Subscriber' that runs every hour by default. This timer job pulls changes from the hub and applies them to subscribing sites.

Each content type has an ID that follows a hierarchical naming convention: '0x' prefix followed by a series of hexadecimal segments. For example, '0x0101' is the base Document content type, and '0x010100...' would be a custom content type inheriting from Document. The ID structure allows content types to inherit from parent content types, forming a hierarchy. When you create a custom content type, you specify a parent (e.g., Document or Item) and inherit its columns and settings. You can then add additional site columns or override inherited settings.

Site columns are defined at the site collection level using a GUID-based schema. Each site column has a type (e.g., Text, Choice, Number, Currency, DateTime, Lookup, Managed Metadata), a default value, and optional settings like required/optional, maximum length, or choice list. When you add a site column to a content type, you are creating a reference to the column definition. This means changes to the site column (e.g., updating the choice list) propagate to all content types and lists that use it. However, changes to the column's settings in a specific list or library can override the site column defaults at the local level.

To create a content type, you navigate to Site Settings > Web Designer Galleries > Site Content Types. Click 'Create' and specify:

After creation, you can add site columns from the 'Site Columns' gallery or create new ones. You can also associate a document template (e.g., a Word file) that will be used when users create new items of this content type. Additionally, you can attach workflows, information management policies (retention, auditing), and custom settings.

To make a content type available across site collections, you must publish it from the Content Type Hub. Steps: 1. Navigate to the Content Type Hub site (usually at https://[tenant].sharepoint.com/sites/contenttypehub). 2. Go to Site Settings > Web Designer Galleries > Site Content Types. 3. Select the content type, then click 'Manage Publishing for this Content Type'. 4. Click 'Publish' to make it available to all subscribing sites. You can also choose to publish to specific site collections.

Once published, the content type appears in the 'Available Site Content Types' list when you add content types to a list or library. The timer job 'Content Type Subscriber' runs every hour to synchronize changes. You can force synchronization by running the following PowerShell command:

Set-SPContentTypeHub -ContentTypeHubUrl "https://tenant.sharepoint.com/sites/contenttypehub" -SiteSubscriptionId <GUID>

Content types often integrate with Managed Metadata (term sets) via Managed Metadata site columns. These columns allow users to tag items with terms from a central term store. When you create a Managed Metadata site column, you bind it to a specific term set. This ensures consistent tagging across the organization. The term store is managed by the Term Store Administrator and can be accessed via the Term Store Management Tool.

SharePoint includes many out-of-the-box content types:

Common site columns include:

When multiple content types are associated with a list, you can set the order in which they appear in the 'New' button menu. You can also mark columns as required, optional, or hidden per content type. This allows different content types to have different column requirements in the same list.

For bulk operations, use SharePoint Online Management Shell or PnP PowerShell:

# Connect to SharePoint Online
Connect-PnPOnline -Url https://tenant.sharepoint.com

# Get all content types
Get-PnPContentType

# Create a new site column
Add-PnPField -DisplayName "Contract Value" -InternalName "ContractValue" -Type Number -Group "Financial"

# Add site column to content type
Add-PnPFieldToContentType -Field "ContractValue" -ContentType "Contract"

# Publish content type from hub
Set-PnPContentTypePublishing -ContentTypeHubUrl "https://tenant.sharepoint.com/sites/contenttypehub"

Content types support versioning. When you modify a published content type, you can choose to create a new version. Subscribing sites can be set to automatically accept new versions or require approval. The 'Content Type Syndication' timer job handles propagation. If a content type is deleted from the hub, it is not automatically removed from subscribing sites; you must manually delete or replace it.

Content types can have policies for retention, auditing, and labeling. These policies are enforced by the SharePoint Information Management Policy feature. For example, you can configure a policy to delete documents after 5 years or to require an audit trail. These policies are tied to the content type and apply wherever the content type is used.

In large enterprises, you set up a Content Type Hub and then configure site collections to subscribe. This is done via the 'Content Type Syndication' feature in Central Administration (on-premises) or by default in SharePoint Online (all site collections automatically subscribe to the hub). In SharePoint Online, you cannot change the hub location; it is fixed at the root site collection. However, you can use the 'Content Type Publishing' feature to control which content types are published and to which sites.

Content type propagation is not instantaneous. The timer job runs hourly, so changes can take up to an hour to appear. If you need immediate propagation, you can manually trigger the timer job using PowerShell or Central Administration. Avoid making frequent changes to published content types, as each change triggers a propagation cycle that can impact performance.

Common issues:

For the MS-102 exam, you need to know:

A large law firm needs to manage contracts, pleadings, and correspondence in a single document library. Previously, they used separate libraries for each type, causing confusion and duplication. By creating content types for 'Contract', 'Pleading', and 'Correspondence', each with specific metadata columns (e.g., 'Case Number', 'Client Name', 'Date Filed'), they consolidated into one library. They published these content types from the Content Type Hub to all practice area site collections. Each content type includes a Word template with pre-formatted headers and a retention policy to delete documents after 7 years. The firm uses Managed Metadata for 'Practice Area' and 'Document Status' to ensure consistent tagging. Performance is smooth with ~500,000 documents. Issues arise when lawyers inadvertently override column defaults, causing inconsistent metadata. The solution is to train users and use PowerShell scripts to enforce column settings from the hub.

A multinational corporation uses SharePoint for HR onboarding. New hires need to complete forms, read policies, and submit documents. They created a 'New Hire Packet' content type with columns for 'Employee ID', 'Start Date', 'Department', and 'Manager'. The content type includes a document template (a Word form) and a workflow that sends notifications to IT and Facilities. The content type is published from the hub to all regional HR site collections. One challenge is that different regions have different departments, so the 'Department' column uses a Managed Metadata term set with regional sub-terms. The timer job propagation delay causes occasional issues when urgent changes are needed; they force synchronization using PowerShell. The system handles 10,000 new hires per year. Misconfiguration often occurs when administrators create content types at the site level instead of using the hub, leading to duplication and inconsistency.

A PMO manages hundreds of projects using a single project site per project. They want standard metadata across all sites: 'Project Name', 'Project Manager', 'Budget', 'Status'. They created a 'Project' content type with these columns and published it to all project sites. Each project site library uses the content type. They also use content type policies to enforce that documents are classified as 'Internal' or 'Confidential'. The PMO uses PowerShell to periodically audit content type usage and ensure no local overrides. A common problem is that when a content type is updated in the hub, existing items in lists do not automatically get new columns; users must manually add the column or use a script to update existing items. They resolve this by running a PowerShell script that adds the new column to all existing items. The scale is 500 project sites with 50,000 documents total.