Go to the homepage
Powered bySitecore Search logo
Skip to main contentThe Editing assets in 3rd-party tools page has loaded.

Editing assets in 3rd-party tools

Context

Requirements might emerge for Sitecore Content Hub users to work with audio, image, and video assets in third-party editing tools, such as Adobe Photoshop, to enhance workflow efficiency and collaboration.

The Sitecore Content Hub Digital Apps Connector uses CI HUB, an in-app connector to more than 57 leading DAM, PIM, CMS, Stock, cloud-storage, and work-management providers worldwide. This tool connects your Sitecore Content Hub instance to the creative service of your choice, such as Adobe Creative Cloud, Microsoft Office, Google Workspace, Figma, or Sketch.

Execution

In a traditional workflow, users must manually download assets from Sitecore Content Hub, edit them in their preferred creative tool, and then re-upload them . This process is inefficient, time-consuming, and prone to versioning issues. By integrating CI HUB, users can streamline content editing and management, eliminating the need for manual downloads/uploads while ensuring version control and collaboration.

As an example workflow:

  • A designer working in Photoshop can access and edit assets directly in the app, eliminating the need to switch between platforms or manually download and upload files.
  • As the designer edits assets in Photoshop, changes are automatically updated, ensuring they’re working with the most current version of the asset.
  • The designer can search for and select Content Hub assets directly within Photoshop, Adobe, Microsoft, Google, Figma, or Sketch, without leaving the application.
  • Once the poster is updated, a marketing team member can access the same assets in PowerPoint through CI HUB, ensuring consistency across teams and platforms without the risk of outdated versions.

Connecting Adobe Photoshop to Sitecore Content Hub via CI HUB

To be able to achieve this, CI HUB needs to be configured, starting with an account setup - see Insights for further detail. Once this is setup, a set of steps need to be followed in Sitecore Content Hub, and in this case Adobe Photoshop.

Before starting, make sure you are logged in to Sitecore Content Hub.

  1. Configure the OAuth Client in Content Hub by following the instructions in the Configure Sitecore Content Hub documentation.
  2. Install the CI HUB Connector for Photoshop - open Adobe Photoshop, Go to Plugins > Browse Plugins. Search for CI HUB Connector for Photoshop and install it.
Browse Plugins in Adobe Photoshop
  1. Connect to Sitecore Content Hub - In Photoshop, go to Plugins > Plugins Panel. Locate and click CI HUB Connector to open the CI HUB panel. In the CI HUB panel, click Add Connection.
Add Connection to CI HUB

Search for Sitecore, select it, and a new browser window will open.

Add Connection to CI HUB

In the browser, enter your Content Hub URL

Login with Sitecore Credentials

Grant access to establish the connection.

Grant Connection to Content Hub
  1. Once connected, several folders will appear in the CI HUB panel: Collections, Assets and Work in Progress (Project assets will also be available if used).
Folders in CI HUB

Collections contains Collections and assets within them. Assets has Assets that are in ‘approved’ state. *Work in Progress *lets you search for and access all your non-approved assets. The approval workflow is also implemented in the WIP folder: rejection reasons are visible and you can submit for approval directly from your Adobe application.

  1. Select an asset and click Use File to open it in Photoshop.
Editing in Photoshop

Authentication & Permissions

Part of the setup, make sure that the users have the right access levels in Content Hub to browse, edit, and save assets.

RolePermissionDetail
CreatorsCreate and SubmitPermissions for assets, enabling them to upload and submit assets for review.
UpdatePermissions for their own assets that are not yet approved.
ReadAccess to the Collections page
Project roleProject specific roles if using Project functionality, based on setup
ApproversApprovePermissions for assets under review, enabling them to approve or reject these assets.
Read and CreateAnnotationsPermissions for assets.
Project roleProject specific roles if using Project functionality, based on setup

See the Security Best Practices documentation for more detail.

Insights

CI HUB Account Setup

After registering for a CI-HUB account, it will automatically be set up with a trial license. If you purchase a subscription through Sitecore, please contact your Account Executive or Sitecore Partner Operations representative to designate a user as the license manager. Once assigned, the designated user must activate their account and can then grant licenses to other users.

The user guide can be downloaded from the CI HUB site.

Differences in User Journey

StageWithout CI HUBWith CI HUB
Access AssetsManually log in to Content Hub, search, and download files.Search and access Content Hub assets directly from the creative tool.
Save, Edit & UploadSave locally, edit, then manually upload to Content Hub.Make changes and save, which syncs automatically with Content Hub.
Approval Process - SubmissionManually log in to Content Hub, find your asset and submit for approval.Submit your asset directly from your creative tool.
Approval Process - Rejection and ReworkManually log in to Content Hub, search, and check the reason your asset approval request was denied. Then download and re-edit your asset.Rejection reasons are visible within your creative tool.
Version ControlRisk of outdated versions being uploaded.Ensures real-time updates and version control.

Further recommendations

To ensure a smooth and efficient workflow, it is critical to follow the best practices below on using CI HUB within Content Hub.

1. Asset Linking & Syncing

  • Users must work with linked assets rather than local copies to maintain version control.
  • Always save assets back to Content Hub through CI HUB to prevent duplicate or outdated versions.
  • Consider making use of Draft Assets - these let you work on a duplicate asset without affecting the original until ready. Once approved, they replace the original asset.

2. File Naming & Metadata

  • Ensure assets follow a consistent naming convention to make searching easier.
  • Use metadata tagging in Content Hub to improve asset discoverability within creative tools.

3. Version Control & Approval Process

  • Enable version tracking in Content Hub to avoid overwriting important assets.
  • Set up approval workflows to ensure only reviewed and approved assets are used in creative projects.

4. Application-Specific Setup

  • Provide training and documentation on how to access Content Hub based on the tool of choice.

Further Documentation

© Copyright 2025, Sitecore. All Rights Reserved

Legal

Privacy

Get Help

LLM