Understanding the Asset Picker

You do not visit the Asset Picker as a separate website. You launch it from within an application that has been integrated with CMP, and it opens over that application’s window.

The Asset Picker is the same component wherever it appears, so the way you search, filter, and select assets is consistent across every integration. Once you are comfortable using it in one application, that experience carries across to the others. The main differences between applications are how you open the Asset Picker and what happens to an asset once you have selected it, both of which are covered in the guide for each application.

The Asset Picker presents assets in one of two ways, depending on how the integration has been set up.

You sign in to your CMP account. In integrations such as Figma and Jira, you enter your tenant and sign in with your company credentials. The Asset Picker then displays the assets you are authorised to see in CMP, and you can search across your whole authorised library.

You choose from a curated collection. In integrations such as CA, an administrator has already set up a managed asset view: a fixed collection of the assets relevant to the task, for example only images for an image field. You pick from that collection without signing in separately.

In both cases you only ever see assets you are entitled to use. When you sign in, your CMP permissions govern what appears; when you choose from a curated collection, the administrator has already limited it to suitable assets.

For the steps involved in signing in, see Use the Asset Picker.

A domain is the organisational unit that determines which assets are visible to you. When you sign in and your CMP account spans more than one domain, the Asset Picker lets you switch between them, so you can reach the assets held in each. This works the same way as switching domains elsewhere in CMP.

When you select assets, the Asset Picker hands them to the application in one of two ways.

Some applications insert a copy of the asset. Figma and Jira work this way, so the asset becomes part of that document and stays as it was when you added it.

Other applications link to the asset by its address in CMP, rather than storing a copy. The application then references the version held in the DAM. Whether later changes in CMP are reflected, and how long a link remains valid, depends on the integration. See the troubleshooting section for the behaviour you might encounter with linked assets.

Whichever way an integration is set up, you only see and select assets you are permitted to use. When you sign in, you do so with your own company credentials, including single sign-on where your organisation uses it, so the application never handles your password directly. This keeps your assets governed by the same permissions that apply throughout CMP, even when you are working in another tool.