General Content Hub FAQ
There are many resources available to help you successfully work with Sitecore Content Hub including best practices, user documentation, cloud development documentation, and the API/SDK documentation. You can also visit the Sitecore website for additional resources such as free training.
The following sections provide answers to common questions about Content Hub and about how to configure Content Hub.
If you don't find an answer to your question in the documentation or this FAQ section, use the Provide feedback form to request more information.
Begin by logging into your Content Hub and then browse through the user guide. You can find additional training resources, including webinars and classes, on the Sitecore Knowledge and Learning portal.
The documentation is constantly evolving to better meet the needs of our users. Please help us improve the documentation by clicking the link available at the bottom of each page.
You manage data models and web pages using options accessed from the Manage page. This includes extending the domain model, managing the sitemap, extending Content Hub with editorial pages (for example, adding pages for brand guidelines), and building pages that allow users to display content stored in the database (such as the most recent assets for a specific brand).
Yes. If you require a full-page preview for a file type other than those supported out of the box, you can create a Pluggable preview. For information about the file types supported in media processing, see Media processing management.
You can duplicate the Search component on other pages or use the variant page on other pages. See Search component.
If you don't specify otherwise in your copy profile, new members have the Ignore method for draft creation and draft merge profiles, and the Keep method for variant profiles.
The Share via email operation is unavailable if you don't have the ShareViaEmail permission for all the assets in your selection. The similar is also true for other bulk operations.
Soft deletion is currently only available for assets. See Trash operation.
The priority of a restore rendition is the same as a refresh rendition, which is the minimum priority and therefore a lower priority than a regular upload.
Yes. The HTML content type has been renamed Rich Text. See Content types.
By default, all taxonomies are published as soon as you create them. You can disable publishing for the whole taxonomy or for any specific taxonomy value. You can disable publishing for a particular taxonomy value by enabling the Don't publish to delivery flag. If you do this, the chosen value is not sent to delivery, but all related entities are.
The following table details the permissions used with watermarking:
|
Permissions |
Enabled? |
Result |
|---|---|---|
|
|
Downloaded previews don't have a watermark. |
|
|
Downloaded previews have a watermark. |
|
|
There is no Preview option available. |
|
|
There is a Preview option on the Orders page and the watermark is applied as required. |
Enabling drafts only adds relations to the schema, without security inheritance or content inheritance. As a result, there is no significant effect on the schema.
You can customize the use cases for variants by adding a new localization operation or changing the existing operation and then selecting the fields (members) that determine the variant entity.
Disabling the feature only removes the UI components and operations that were made available for variants. Created copy profiles and configurations are unaffected. You can use them again if you re-enable variants.
No. Although both are needed from a schema standpoint and for the operation configuration, mandatory fields and variant operations are independent. If a field is mandatory, the creation dialog box does not allow you to create a variant until you complete the field (schema requirement) with a value that is different from the original value (operation mandatory field requirement).
Yes. For more information on variant configurations, see Variants.
The filter is not shown in the user interface because the UI component does not render this type of filter.