This glossary provides explanations for some of the key Sitecore Content Hub terms and concepts.

ActionComponents that perform a specific task. Manually triggered by a user from the UI, automatically run by a trigger or by the API.
AdministratorA Sitecore employee responsible for the upkeep, configuration, and reliable operation of Content Hub (customers cannot be administrators). Can edit or delete any system-owned entity.
AgentComponent configured to perform a specific type of task.
AssetEntities in Content Hub such as images, videos, or text files.
CampaignAction plan to promote a product.
CollectionA set of assets grouped together. For example, a collection can group related assets based on an event or a product. Collections make it easy to share content with collaborators.
ContentElement of a campaign such as a blog post, a recipe or an advertisement.
Domain modelDefines the domain parts of a system and how these parts are structured and linked together. In Content Hub, the domain model is a representation of the entity types stored in Sitecore DAM and how they are related to and inherit information from each other.
Content collectionA content collection brings together content items that have a common property or purpose. It enables you to create, manage, and share channel-specific content for easy reuse.
DraftTemporary instance of an item that lets you make modifications without starting the creation and approval process from the start. For example, you can create a draft of a published recipe content that you want to update. The original recipe content stays available but is locked while you edit the draft. When your draft is ready, you send it through an approval workflow for the changes to be approved and merged into the published version, at which point the draft disappears.
DRMDigital Rights Management. Access control technologies used to restrict usage of copyrighted works.
EntityA set of data that belongs together (such as for a product, campaign, project, story, recipe, or asset). In general, an entity is anything that you can find and display when searching for content. For example, an entity can be a digital asset (file) that has been uploaded along with its metadata or it can be a collection of related data. An entity from another system linked to Sitecore DAM is called a proxy entity. You use proxy entities in Content Hub like any other entity. They are, however, read-only because master-data ownership for this type of entity belongs to the other system.
Entity definitionSet of metadata properties that define how an entity is structured. The definition includes both descriptive metadata properties and relations with other entities. You can also think of the entity definition as a content type definition or an entity-specific metadata schema.
Entity propertyEditable detail about an entity (such as product number, benefit, campaign brief, or file size). Properties can be, for example, text, numbers, option lists, or dates. They can be multilingual and you can define as many properties as you need on an entity. You can also specify properties to a proxy entity that are not available in the source system.
FragmentFragments are much like assets, except that the content is a text snippet rather than a media file. A fragment consists of a rich-text snippet and a title.
JobA background process.
Job (MRM)A single space in which teams and departments can work together.
MembersThe properties and relations you assign to an entity definition.
Member groupsA collection of members.
Page componentA container that holds the actual content on a page.
PolicyA user group policy that consists of rules, conditions, and permissions. Policies grant permissions to users, which determines what they can see and do.
Portal assetAn asset created specifically for a portal page.
Portal pageA page from which you can access and interact with data (such as entities, components, relations, and properties). Users need access to the appropriate portal pages to see the content.
Preview (feature)Preview features are available in early access for you to provide feedback. They are not supported by the Sitecore support team. They might have limited or restricted functionality. They are not meant for production and might be available only in selected geographic areas.
ProductEntities in Sitecore Product Content Management (PCM) representing a product.
ProjectMarketing plan in Sitecore Marketing Resource Management (MRM).
Public linkFree access link to an asset.
RelationLink between two entities that lets you display the data on detail pages from the parent-child direct relationship. By creating relations between entities, you make each entity more defined and richer without duplicating data. For example, you might have a product that is available in several colors, a recipe that uses several products, or a campaign that contains a story along with associated files and, in each case, there is a relation between the parent and the children entities.
RenditionVersion of an asset. For example, images can have original and medium-size renditions.
SchemaSee entity definition.
Search (saved search)The result of a search in Content Hub saved as an entity object.
Security modelThe conditions for securing and granting user permissions to access entity definitions.
Selection (saved selection)Selection of assets saved as an entity object.
SuperuserA user with special privileges to configure and maintain a Content Hub solution. Can edit or delete any non-system-owned entity.
System-ownedSettings, definitions, properties, or components that are default elements in Content Hub. Superusers cannot edit these default elements.
State flowThe digital logic within the content creation process. A series of states, transitions, and actions that superusers can enable for any type of content.
TaskAction performed by a user in a project.
Taxonomy relationThe relation between entities that allows for advanced metadata and security inheritance through their family tree.
Taxonomy definitionEntity definition that is searchable as a facet in advanced searches.
TemplatePre-defined structure and default values to help build the domain model.
TransformationProcessing operation that allows superusers to manage the configuration of preset asset renditions and apply them to renditions dynamically.
TriggerConditions that, when met, automatically execute a set of actions.
VariantStand-alone copy of an original item that has at least one different property. This variant is considered a sibling or a child of the original item. Variants can be used to adapt an item to different locales, for example.
VersionRevision of an original content item that remains associated with the original, essentially an instance of a content item that you can make changes to without affecting the original. The main difference between drafts and versions is that drafts always merge into the original, hence disappear once you are satisfied with the changes you made, while versions are different instances of the same content item. The latest version is considered the master version, but you can revert to an earlier version if necessary.

Can we improve this article ? Provide feedback