SharePoint Content Type Hub: Modern Setup and SharePoint 2013 Context

A SharePoint content type hub provides a central place to define and publish reusable content types. In SharePoint Online, administrators work through the Content type gallery in the SharePoint admin centre or the tenant's /sites/ContentTypeHub site. Publication makes a type available to sites, but propagation is not an instant transaction.

The original version of this article described SharePoint 2013. The concept survives, while the administration model has changed.

What belongs in a content type

A content type can combine:

• a document or item type
• reusable site columns
• a document template
• information-management settings
• behaviours relevant to that class of content

Use it when several sites need the same meaning for fields such as policy owner, review date or contract type. Do not create a global content type for a one-off list.

Design before publishing

Agree:

1. the business name and purpose
2. column names, types and required status
3. which values use managed metadata
4. who owns future changes
5. which sites should consume it
6. how a breaking change will be introduced

Internal names and field types are awkward to change later. Pilot with representative libraries before broad publication.

Publish in SharePoint Online

You need the appropriate SharePoint administrative permissions. Microsoft notes that the gallery is not available to the Global Reader role.

1. Open the SharePoint admin centre.
2. Select Content services, then Content type gallery.
3. Create or select the content type.
4. Add the required site columns and settings.
5. Select the content type, then Publish.
6. Wait for distribution and verify it in a pilot site.

Microsoft's publish procedure also distinguishes:

• Publish to make the type available
• Republish to distribute updates
• Unpublish to stop future download, while copies already in use become local content types

Unpublish is not the same as deleting content or removing a type safely from libraries.

Add and test the published type

In a pilot library:

1. enable management of content types if required
2. add the published content type
3. create a representative item or document
4. check required fields, defaults, templates and views
5. edit the central type and republish a harmless test change
6. confirm when and how the change appears

Microsoft's enterprise content-management guidance warns that replication can take time depending on the tenant and associated data. Do not build an operational process around a promised five-minute sync.

Pushing content types to hub-associated sites

Microsoft also documents a capability to push published content types to selected hubs. That feature has its own licensing requirement and works only with types that are already published.

Confirm the current licence and rollout in your tenant before using it in the design. Ordinary publication and licensed push-to-hub behaviour are not the same thing.

SharePoint 2013 and other on-premises farms

In SharePoint 2013, the content type hub is tied to a Managed Metadata service application. Timer jobs distribute published types to subscribed web applications and site collections.

For a legacy farm, document:

• the hub site collection
• the Managed Metadata service application and connections
• subscriber web applications
• content-type and content-type-subscriber timer jobs
• farm build and support status

Do not apply SharePoint Online admin-centre instructions to an on-premises farm. Do not modify the content database directly to force syndication.

Common problems

• The type is absent: confirm it is published, the site can consume it and distribution has completed.
• An update is absent: republish, then check propagation rather than recreating the type locally.
• A local copy diverged: establish whether the site customised a syndicated type.
• A column is wrong everywhere: stop propagation and design a compatible replacement or controlled repair.
• A Multi-Geo tenant behaves differently: Microsoft documents one content type hub per geo, with different publication behaviour to understand.

Proof boundary

Seeing the content type in one pilot library proves availability there. It does not prove every site has received it or that existing documents have been reclassified correctly. Use an inventory or migration report for tenant-wide claims.

Sources

• Publish a content type
• Enterprise Content Management and content type hubs
• Push content types to a hub
• Content types in a Multi-Geo tenant

For practical metadata and information-architecture discussions, join the SharePoint & Teams Admins Space.