Sitecore Content Hub Features

Ingestion & storage

• Upload channels: web UI upload (governed by upload configurations), Upload API v2, fetch jobs (Content Hub pulls files from URLs), Excel import (metadata/assets), package import, Digital Apps Connector (CI HUB) from creative/Office tools S35 S38 S77 S86.
• Upload configurations (M.UploadConfiguration) set allowed extensions, maximum file size, target repository and initial lifecycle status; upload permissions are applied per configuration S35.
• File size: maximum configurable per upload configuration, with an Azure Blob ceiling of 4.7 TB (same for fetch jobs); API uploads are chunked in ≤ 10 MB parts S35 S36 S38.
• Bulk guidance: the Upload API is meant for day-to-day uploads/custom UIs, not bulk; Sitecore recommends fetch jobs or Excel import for bulk and migrations S56 S35.
• Supported formats (default media processing): images (incl. RAW formats, WebP, JPEG 2000, BPG), vectors (AI, EPS, PSD/PSB, SVG, TIFF), GIF, Office documents, email (EML/MSG), PDF, HTML, audio (AIF/AIFF, M4A, MP3, WAV), video (AVI, FLV, M4V, MOV, MP4, MPEG, WEBM, WMV), archives, colour profiles, subtitles, InDesign; executables and scripts (.exe, .bat, .ps1, .jar…) are blocked S65.
• Versioning: new main file on an existing asset (NewMainFile action) moves the previous file to the file history; alternative files supported S35 S38.
• Archive tier: only Approved assets can be archived; the original and non-essential renditions move to archive storage, public links are disabled (after cache expiry), non-essential renditions are deleted after 30 days by default (ArchivedAssetsCleaner setting); archived assets stay viewable through essential renditions and can be restored S58 S87 S139.
• Duplicate detection: no duplicate-detection page appears in the current Content Hub doc indexes S130 — Unknown Unverified (third-party material mentions a DuplicateDetection setting and a file digest; not verified on a primary source).
• Trash: soft-deleted assets go to per-user My trash and an admin Trash page, with restore or permanent delete S137.

Metadata & taxonomy

• Schema = entity definitions made of member groups, properties and relations; administered in Manage → Schema; schema changes may trigger a graph rebuild that pauses regular operations (publish outside business hours) S60; Sitecore reported that its 2026-10-02 main-database network upgrade cut graph rebuild completion time by up to 50%, varying by operation, environment and workload (no customer action) S161.
• Property types: String (single-line, multiline, HTML), Integer, Long, Decimal, Boolean, DateTime, DateTimeOffset, JSON, plus option-list-bound strings; flags for mandatory, multilanguage, multivalue, indexed, unique, regex validation, conditional visibility/required rules S3 S60.
• Taxonomies vs option lists: taxonomies are entities (unlimited hierarchy depth, can drive security, facets and extra properties; keep below ~300 values and 250 facets per definition); option lists are simple controlled vocabularies (< 50 recommended, < 100 max, 5 hierarchy levels, no security) S56 S61.
• Multilingual metadata: properties can be multilanguage; cultures configured per tenant S33.
• Embedded metadata: ExifTool extracts file metadata into a per-asset metadata.json rendition S58 S136; mapping to properties via the ImportMetadataConfiguration setting (single-value properties and option lists) or metadata-processing scripts (also multi-value, relations, taxonomies) S136. Write-back of metadata into files on download: Unknown.
• Bulk edit: Excel export/edit/re-import, in-table editing ("Edit in table"), and API mass-edit jobs S86 S138 S39.
• Validation: mandatory members and conditional rules are enforced when content is validated (lifecycle/state flows) S3 S73.

Search & discovery

• Search components configured per page (facets, filters, sorting, full-text, saved searches) driven by named search configurations; default paging 50 items × 100 pages S40.
• Full-text search with operators; facets on taxonomies and indexed fields S6 S40.
• AI-assisted visual search: find images by colour, text description or an uploaded example image (JPG/JPEG/PNG); usage guidance published S54 S75. Marketed "without usage limits" S101.
• Collections: shareable groupings of asset references with comments S74.
• Natural-language / conversational search: Brand Assistant and AI features (see below); a dedicated natural-language DAM search beyond visual search is Unknown.

AI capabilities

AI governance: Azure OpenAI; Sitecore states it does not store prompts or responses; most AI features need to be enabled by a superuser and require Sitecore Stream S54. C2PA provenance support is claimed on the product page S101; its detailed behaviour was not verified in the docs (Unknown). Per-tenant opt-out: AI is opt-in (disabled until enabled) S54.

Organization

• No folder tree by default: assets are organised by metadata and taxonomy relations (e.g. asset type, brand), surfaced as facets S32 S61.
• Collections (manual groupings, shareable, public collections via privilege PublishCollection) S63 S74.
• Portal pages: the whole UI is a configurable portal (pages, components, themes, languages) S56.
• Brand hubs / style guides: brand kits exist for AI brand awareness S54; a dedicated public brand-guidelines site builder is Unknown.

Workflow & collaboration

• Asset lifecycle: Created → Under review → Approved / Rejected → Archived, with direct publish, soft delete and restore; exposed as lifecycle operations S2.
• State flows: configurable state machines for any entity, with parallel and sequential approvals and configurable approval/rejection rules S73. Since 2026-10-02 the Selection component supports guarded state-flow transitions, so users with the required permissions (not itemised) can approve, reject or override several selected entities in one mass action S164.
• Annotations / proofing: annotate images, documents, video and audio, @-mention users, annotation reports, version comparison S82.
• Comment HTML sanitisation (2026-10-02): an opt-in CommentHtmlSanitization setting in PortalConfiguration restricts the HTML tags, attributes and CSS properties allowed in user comments (style allow-list) and limits image URLs to trusted hosts, against HTML injection and data exfiltration; it also applies to comments submitted through the API. The changelog presents it as optional and something admins "can now enable" (default state and allow-list syntax not stated there) S163.
• Content operations (licence DAM with Content Ops): campaigns, content items, briefs, projects/jobs/tasks, drafts, localisation S68 S138.
• Creative integrations: Digital Apps Connector (Adobe CC, Office, Google Workspace, Figma, Sketch via CI HUB), legacy Sitecore Connect for Creative Cloud (being deprecated) S77 S78.

Rights & governance

• Security model: user groups with policies (rules per definition with conditions and permissions), member security (read/write on secured members) and system privileges; permissions are positive only; multiple group policies combine with Any or All S62 S63.
• Permissions used in policies include Read, Download, Create, Update, Submit, Approve, CreateAnnotations, ViewNotWatermarked (examples from the security best practices), plus ViewFileHistory / ViewDataHistory (which need the ReadAudit privilege) S63 S85.
• Digital rights management: rights profiles and DRM contracts; restricted assets require a compliant intended use or an approved download request; public links to restricted assets return 404 S83.
• Watermarking of image/PDF renditions based on user permissions (not on public links) S71.
• Audit trail: business, user/security, raw, action, scripting and trigger logs, queryable in UI and API; retention 2 years online / 7 years offline for security and audit events in production S57 S9.
• Security diagnostics tool to inspect effective permissions and duplicate rules S85.
• Retention: trash and archive cleanup settings exist; asset retention policies beyond these are Unknown.

Distribution & delivery

• Public links: unsigned, cacheable static URLs to renditions, optional expiry, indexable by search engines by default, 10-minute cache with a version parameter S70 S52.
• Media transformations on public links (resize, crop, blur, background, brightness…, Cloudflare-based) for JPEG, PNG, GIF, WebP, HEIC S52.
• Delivery links (pre-signed, ~20-minute validity) and gateway links (require an authenticated user/OAuth token) S84 S53.
• Media Delivery Service with Cloudflare CDN S53.
• Experience Edge: GraphQL Preview/Delivery APIs for headless delivery of published content S47.
• Download orders (zipped multi-asset downloads with optional watermarking) S12 S71.
• Templating / print: Sitecore Content Publisher (CHILI engine) smart templates and publications; print entity generation (PDF) S79 S44.

Video & rich media

• Video, audio and document previews via renditions; video annotations S58 S82.
• Subtitles: SRT and SUB (VobSub text) upload S66.
• Video AI via Azure Video Indexer (see AI table) S76.
• 3D: ZIP packages rendered with a simple built-in 3D preview (asset type must trigger archive extraction) S67.
• Adaptive streaming / transcoding profiles: Unknown (not documented in the pages read).

Analytics & reporting

• Reporting dashboard: live overview (asset counts by type) and historical overview (uploads, logins, downloads, top 25 downloads), customisable with chart components S72.
• Reporting/audit logs exportable (download orders) and queryable via the Audit API with aggregations S9.
• Usage tracking: users, monthly business users, API keys, OAuth clients, storage, bandwidth, video indexing, modules via /api/usagetracking S42.
• System status/statistics (storage, queues, search, users) via the Status API S10.

Administration

• User provisioning: SSO with several external providers, auto-creation of users configurable; Excel-based user management S64 S130. SCIM: not found (Unknown).
• Environments: separate Dev, QA and PRD tenants; Dev tenants have hard limits (100 API calls/min, 10,500 custom and 10,500 taxonomy entities, 2-week audit retention) S23.
• Configuration as data: settings, schema, policies, scripts, triggers, taxonomies and pages are exported/imported as packages (UI or ch-cli) S51 S86.
• Extensibility: scripts, triggers and actions, external (React) UI components S43 S44 S130.
• Multi-brand: brand separation relies on taxonomies + policies within one tenant S61 S62; multiple tenants per customer are possible (Dev/QA/PRD) S23.
• Licences: per-module seats visible in Manage → Stats → License S69.