Skip to main content

Content Type Gallery

The Content Type Gallery is the tenant-level home for shared content types in SharePoint Online, found in the SharePoint admin center. Content types created here - Contracts, Policies, Invoices, and other enterprise standards - are defined once, published, and made available to every site in the organization, so the same structure and tagging exist everywhere without rebuilding them site by site. It is the modern successor to the Content Type Hub.
Related Features
Content Type, Document Set, Site Columns

Common Use Cases

  • Enterprise content standardization: define official content types and standard tagging structures used across the organization
  • Central metadata management: maintain one authoritative set of columns and settings
  • Content Type publishing: push content types to other SharePoint sites
  • Governance at scale: enforce naming, metadata, and compliance standards tenant-wide
  • Large environments: reduce duplication in multi-site or multi-hub architectures

Benefits

  • Define once, use everywhere: a content type built and published in the gallery becomes available to every site in the tenant, with no rebuilding site by site
  • Central updates: edit the master in the gallery and choose Republish, and every consuming site and library picks up the new version
  • Modern admin experience: the gallery is the cleaner successor to the Content Type Hub, managing the same publishing engine from the SharePoint admin center
  • One structure for governance: the same columns and tagging everywhere make retention, compliance, and search configuration far easier to standardize
  • Controlled versioning: the master copy is edited and versioned centrally in the gallery, so administrators decide exactly what goes out and when
  • Graceful retirement: unpublishing converts in-use copies to local content types, so existing documents and libraries keep working when a standard is withdrawn

How It Works

  • Publish-and-consume model: administrators define and publish content types centrally in the gallery, and sites across the tenant pull them in for use in their lists and libraries
  • Created like site content types: you define the name, description, category, parent, and columns, just at the tenant level
  • Publish controls availability: until a content type is published, it exists only in the gallery; publishing makes it available to every site in the organization
  • Consuming sites get managed copies: published content types arrive as centrally managed copies, while the master is edited and versioned in the gallery
  • Republish distributes updates: choosing Republish rolls your changes out so every consuming site and library picks up the new version
  • Successor to the Content Type Hub: the gallery is the modern interface for the hub site at /sites/ContentTypeHub, and both manage the same underlying publishing engine
  • Pull by default, push with premium: standard publishing relies on sites pulling from the gallery, while pushing a content type automatically to every site in a hub is a premium add-on capability

Limits and Nuances

  • Plan before publishing: published content types land in every site, so a poorly built one propagates everywhere and is painful to walk back; treat each publish like a production release
  • Column choices travel: each attached column’s optional, required, or hidden setting goes out with the publish, so settle those before distributing
  • Publishing alone configures nothing: every consuming list and library must still enable content type management and add the published type
  • Republishing hits everything at once: updates reach all consuming sites and libraries simultaneously, so test changes on a single site first
  • Unpublishing converts copies to local: they keep working but lose their connection to the gallery and stop receiving updates
  • Admin permissions required: the gallery needs SharePoint admin rights; it is not available to the Global Reader role, and site owners cannot publish from it
  • Distribution is pull-based and not instant: allow time for newly published types to appear on sites, and automatic push to hub-associated sites requires a premium license
  • Not mandatory for everyone: smaller environments with a handful of sites can manage content types locally and skip tenant publishing entirely

Common Questions About the Content Type Gallery

What is the Content Type Gallery in SharePoint?

The Content Type Gallery is a tenant-level area in the SharePoint admin center where administrators create, manage, and publish content types for the entire organization. Instead of rebuilding the same Contract or Policy content type on every site, you define it once in the gallery, publish it, and every SharePoint site can consume it – giving the whole tenant one consistent content structure.

How is the Content Type Gallery different from the Content Type Hub?

They are two interfaces to the same publishing engine. The original Content Type Hub is a hidden site collection at /sites/ContentTypeHub that has handled enterprise content type publishing for years. The Content Type Gallery is its modern replacement inside the SharePoint admin center, with a cleaner interface for creating, editing, and publishing. Content types published from either location behave the same way on consuming sites.

How do I publish a content type to all sites?

In the SharePoint admin center, open Content services and then Content type gallery, select the content type, and choose Publish from the menu bar. The Manage Publishing panel offers three options: Publish to make it available to all sites, Republish to distribute updates, and Unpublish to stop distribution. After saving, sites across the tenant can add the content type to their lists and libraries.

What happens when I unpublish a content type?

Unpublishing stops distribution, but nothing breaks. Any copies of the content type already in use on sites are converted to local content types – existing documents keep their metadata, libraries keep working, and the columns stay in place. What changes is the connection: those local copies no longer receive updates when the gallery version changes, and each site manages its copy independently from then on.

Do published content types show up in libraries automatically?

No, and this surprises many site owners. Publishing makes a content type available to sites, but each list or library must still opt in – the library needs Allow management of content types switched on in its Advanced settings, and the published content type must be added to it. Plan for that last-mile configuration when rolling out enterprise content types.

When is the Content Type Gallery worth using?

It earns its keep when the same content structures need to exist across many sites – think organizations with dozens of department sites all storing contracts, policies, or project documents. For a tenant with a handful of sites, local content types are simpler. Greg’s rule of thumb for clients: once you catch yourself recreating the same content type on a third site, it is time to move it to the gallery.