Asset Bank can connect with other systems in a number of ways - from giving designers direct access to approved assets within Adobe Creative Cloud or Canva, to connecting with your website, CMS or other business systems while retaining the information people need to use content appropriately.

The best approach depends on what you're trying to connect and what you want the connection to achieve.

This page provides an overview of the main options and links to more detailed information.

1. Connect Asset Bank to apps you already use

Asset Bank has ready-made integrations with a range of creative, productivity and content platforms.

CI HUB - Adobe, Canva, Microsoft 365 and more

Best for: Giving users direct access to Asset Bank from within the applications they already use.

Our integration partner CI HUB connects Asset Bank with a growing range of creative and productivity applications, including:

• Adobe Creative Cloud
• Canva
• Microsoft 365
• Google Workspace
• Figma and Sketch
• SharePoint
• WordPress

Once connected, users can search and browse Asset Bank and access approved assets without repeatedly switching applications, downloading files and uploading them again. Asset Bank permissions are respected, helping ensure users continue to work with content they're authorised to access. 

Key compliance metadata, such as expiry dates, usage rights and additional usage limitations, can also be displayed within connected applications. This helps designers understand how an asset can be used without leaving the application, so they can work with approved content confidently. 

Finally, some applications also support workflows such as uploading finished work or new versions back into Asset Bank.

Find out more:

CI HUB overview

Asset Bank integrations

Sitecore - connect Asset Bank to your CMS

Best for: Teams using Sitecore that want easy access to approved Asset Bank content from their CMS.

Asset Bank has a dedicated integration with Sitecore, making Asset Bank assets available through the Sitecore Media Library. (Please note, this only works with Sitecore on-premise installations.)

This allows website editors to find and use approved content without having to manually download it from Asset Bank and upload it to Sitecore.

Find out more:

Asset Bank and Sitecore

Shutterstock - bring licensed stock imagery into Asset Bank

Best for: Teams that regularly license Shutterstock imagery and want it automatically centralised in their DAM.

Asset Bank's Shutterstock Premier integration can automatically import licensed Shutterstock images into Asset Bank, along with their associated tags and metadata.

This removes the need to manually download imagery from Shutterstock and upload it into Asset Bank, while helping ensure licensed stock content is stored centrally and can be easily found and reused.

Find out more:

Asset Bank and Shutterstock

Ziflow - creative review and approval

Best for: Teams that need a structured review, feedback and approval process for creative content.

Ziflow is an online proofing platform for managing the review and approval of creative content.

Once artwork has been reviewed and approved in Ziflow, the completed file is automatically sent to a nominated folder in Asset Bank. A link back to Ziflow is retained, making it easy to view the approval history and see who approved the artwork and when.

Find out more:

Asset Bank and Ziflow

BrandStencil and We Brand - create on-brand content

Best for: Organisations that want users to create their own branded materials using controlled templates and approved assets.

Asset Bank can integrate with templating platforms including BrandStencil and We Brand.

These integrations can help organisations combine centrally managed Asset Bank content with controlled templates, enabling users to create materials themselves while maintaining brand consistency.

For example, Leonard Cheshire integrated Asset Bank with BrandStencil to allow teams across the organisation to create their own on-brand marketing materials.

Find out more:

Asset Bank and BrandStencil

Asset Bank and We Brand

Leonard Cheshire case study

2. Connect Asset Bank to your own systems

If there isn't an existing integration for the system you use, there are several ways to build your own connection to Asset Bank.

REST API - build a bespoke integration

Best for: Connecting Asset Bank to another business system or building your own integration.

Asset Bank provides a REST API that allows external applications to interact with your Asset Bank.

For example, an integration could:

• Search for assets
• Retrieve and download assets
• Retrieve and review compliance metadata, including expiry dates, usage rights and other limitations
• Upload new assets
• Add or update metadata
• Connect Asset Bank with another internal or third-party application

The API can also be used to support compliance-focused workflows. For example, another system could check whether content is still approved for use, identify approaching expiry dates, or retrieve limitations relating to geographical regions, channels or other permitted uses.

The API uses OAuth 2.0 authentication and is available with Professional and Enterprise subscriptions.

Find out more:

Asset Bank API overview and Postman guide

API rate limiting

Asset Bank integrations

Asset Transformer - use Asset Bank images on your website

Best for: Websites, e-commerce sites and product catalogues that need web-ready versions of images held in Asset Bank.

The Asset Transformer Module allows Asset Bank to act as the source for images displayed on your websites.

Rather than maintaining multiple copies of an image, you can keep a high-resolution master in Asset Bank and request appropriately sized or cropped versions for use on your website.

This is particularly useful for organisations that want Asset Bank to remain the single source of truth for product or website imagery.

Find out more:

Asset Transformer Module

CMS Integration - select Asset Bank content from your CMS

Best for: Allowing website editors to find and select approved Asset Bank content without leaving their CMS.

Asset Bank's CMS Integration Module provides a way to integrate Asset Bank with your own CMS.

A "Select asset from Asset Bank" option can be added to your CMS. When an editor needs an image, they can open Asset Bank, find the appropriate asset, select the required size or crop and insert it into their content.

This can provide a useful alternative to building a more complex API integration where the primary requirement is simply to give website editors easy access to approved assets.

Find out more:

CMS Integration configuration

Asset Bank integrations

Publishing Module - automatically send assets somewhere else

Best for: Regularly transferring selected assets from Asset Bank to another server, system or file location.

Sometimes another system doesn't need a live connection to Asset Bank - it simply needs Asset Bank to provide it with an up-to-date set of files.

The Publishing Module allows you to define criteria for the assets you want to publish and periodically transfer matching files to another location.

For example, you might publish:

• Current product images
• Assets approved for use on a particular website
• Images belonging to a particular department or campaign
• Web-sized versions of selected assets

Publishing can run automatically at a specified interval or be triggered manually.

This can be a simpler alternative to building an API integration where the receiving system simply needs an up-to-date collection of files.

Find out more:

Publishing overview

Asset Bank integrations

3. Connect Asset Bank to your IT infrastructure

Single Sign-On (SSO)

Best for: Allowing users to access Asset Bank using their existing organisational login.

Integration isn't always about moving assets between systems. Asset Bank can also integrate with your organisation's identity and authentication infrastructure using Single Sign-On (SSO).

This can make access simpler for users while allowing your IT team to manage authentication centrally.

Asset Bank supports SAML 2.0 compatible identity providers as well as LDAP-based configurations.

Find out more:

Asset Bank Technical Services

Which option should I use?

Here's a quick guide:

Not sure which option is right for you?

There can be more than one way to connect Asset Bank to another system.

For example, if you want to connect Asset Bank to your website, the right approach might be Asset Transformer, CMS Integration, Publishing or the REST API, depending on how your website works and what you want the connection to achieve.

If you're unsure, contact the Asset Bank Support team and tell us:

• Which system you want to connect to Asset Bank
• What you want the connection to achieve

We can then help you identify the most appropriate approach.

What if I don't see the tool I want to connect to?

If the tool you're looking for isn't listed above, we don't currently offer a pre-built integration for it.

You can still contact the Asset Bank Support team and tell us which tool you'd like to connect. We'll record your request in our ideas backlog, where it can be considered alongside requests from other customers.

We focus our development and ongoing maintenance efforts on integrations with the most widely requested tools and platforms, so we can't guarantee that a particular integration will be developed or provide a timeframe for when it might become available.

In the meantime, there may be another way to achieve what you need. Depending on the system and your requirements, options such as our REST API, CMS Integration, Publishing Module or Asset Transformer may provide an alternative.

When contacting us, it's helpful to tell us both which system you'd like to connect and what you'd like the integration to achieve. This helps us understand your requirement and suggest the most appropriate options.