As an administrator, you can perform several tasks related to asset management.
Some of these tasks involve configuring settings that enable functionality for your users, and others involve managing assets directly:
- Creating named transformations: Create sets of pre-defined transformations that can be used for:
- Configuring access control: Determine who can access an asset and when.
- Moderating assets: Moderate assets when they're uploaded to keep unwanted content out of your system.
- Register for add-ons: Enable add-ons to extend your DAM functionality.
A named transformation is a pre-defined set of transformations that has been given a name for easy reference. Named transformations simplify applying transformations programmatically, allowing several, possibly complex transformations to be referred to with one concise name. Similarly, named transformations shorten URLs and improve SEO, because transformations can be referred to using one concise name within the URL.
Additionally, named transformations can be set as transformation presets and strict transformations, which enable additional functionality:
Especially useful for a DAM administrator, setting a named transformation as a transformation preset enables your account users to apply that named transformation to assets for preview and/or download at the click of a button.
You can also allow a named transformation for a strict transformation. The Strict transformations setting prevents end users from dynamically applying transformations to media assets by changing their URLs. If this setting is on, you can specifically allow a named transformation to be applied to assets dynamically as an exception.
You can coordinate with developers on your team to create and manage named transformations programmatically, or you can create and manage named transformations via the console UI using the Transformation Editor or the new Transformation Builder (Beta).
You can create a named transformation using the Transformations UI in your Cloudinary console:
To create a named transformation using the console, you have a few options:
- Start with a cookbook recipe as a template and refine it to your needs before saving it with your chosen name.
- View a list of all your dynamic transformations (those that were generated and delivered on the fly) and save one of those with your chosen name.
- Create a new transformation from scratch using the Transformation Editor or Transformation Builder (Beta) and save with your chosen name.
- Must contain valid UTF8 characters only
- Must not contain more than 1024 characters
- Must not contain any of these characters:
Once you've saved your named transformations, you can view a list of them on the Named Transformations page of the console. From here, you can edit or copy the named transformation.
The Cloudinary Transformation Builder is a brand new UI designed to help you create and save your transformations in a simple and easy to use way.
Here are some of the features and functionality you can get by using the builder:
- Simple and intuitive UI for selecting and configuring transformation actions - easily discover actions and parameters as you build.
- Transformations built as a series of self-contained actions so you can see the results of each one as you apply it.
- Ability to update the default preview image to something from your own Media Library.
- Developers can copy URL and SDK snippets directly into their code.
A transformation preset can be applied to an image to generate a version modified according to a set of pre-defined transformations (i.e., a named transformation).
Transformation presets can be applied in the following contexts:
- DAM users can preview an image with transformation presets applied from the Manage page to see how the selected image would look with those transformations applied. Users can perform operations such as opening the displayed image in a new tab, downloading it, copying the URL, or further editing the transformation.
- Depending on settings, external stakeholders may be able to download assets with transformation presets applied from published collections and media portals. This functionality enables modified images to be shared with external stakeholders instead of originals.
Several transformation presets are provided by default, and you can add your own by setting named transformations as transformation presets, up to a maximum of 30 in total.
To set an existing named transformation as a transformation preset:
- In the Named Transformations page of the Management console, hover over the named transformation you want to use as a transformation preset and open the menu using the kebab (3 dots) icon.
- From the menu, turn on the Show in image presets option.
Make sure the named transformation definition doesn't include any video-specific transformations or user-defined variables.
- Transformation presets can be a convenient way to see how an image may look with different levels of compression applied. To create a preset for this purpose, create a new named transformation, set the Quality option to the desired compression level, and give the named transformation an appropriate name, such as "Good quality mode" or similar. Then select to Show in image presets as described above. You can select Auto for your quality setting and Cloudinary will automatically apply the compression that achieves the optimal balance between file size and visual quality to your asset.
- When you click a transformation preset in the Management drill-down page to preview an image with that preset, it doesn't count against your account's transformation quota. However, the first time someone views that preset transformation for a specific asset outside the Media Library (open in a browser tab, download, etc.), a derived image is generated for your account and counts like any other image transformation.
- You can make transformation presets available from published collections and Media Portals. When available, external stakeholders accessing published collections or portals can download assets transformed by a preset, instead of, or in addition to, being able to download originals.
Keep in mind that external stakeholders won't be able to preview the transformation presets. Use descriptive names to make it easier to anticipate what the transformation presets will do.
When transformations are added to Cloudinary asset delivery URLs the transformed assets are generated dynamically, meaning that if the requested transformed asset does not already exist, then it is created on the fly. This is a powerful feature, but you may not want your end users to play with these options on your assets.
Enabling the Strict transformations setting prevents unexpected transformations from being charged to your account by blocking end users, who have access to your delivered assets via your website or app, from dynamically generating transformations on them.
If this setting is on, you can allow specific named transformations to be used dynamically as an exception.
Enable the Strict Transformations setting in your account console's Security settings. To mark a specific transformation as allowed, open the Named Transformations page of the console. Next to each transformation you can open the menu and toggle to either allow or restrict the transformation.
When working with Cloudinary's API, there are a few ways you can control who can access an asset and when. These include:
- Storing an asset with an
- Applying the
access_controlparameter (premium feature)
If the first option above is applied on an asset, the asset's current access control mode is indicated in the Media Library with an icon, but you can't apply or modify the setting via the Media Library. It can be applied or modified only programmatically via the API. For more details, see Control access to assets during upload and Media access control on delivery.
access_control option can be set programmatically via the API or via the Media Library.
If your account is enabled for the
access_control option, an account administrator can change any asset's access control mode between Public and Restricted directly from the Media Library.
Setting an asset as Restricted means that people can only view that asset outside the Media Library if they have both the asset URL and an authentication token (a special type of validation for ensuring that a person requesting a URL is allowed to access it), except during an optional time-limited date range when the asset is defined as publicly accessible.
Time-limited restricted access can be useful if you have an image or video that's intended to be used for a special campaign or that shows a new product design, and it's imperative that the asset will not be shared outside the organization prior to an official launch date. Or conversely, you may have assets that you no longer want the public to be able to view or share after the content is obsolete.
When working with the
access_control option, you can change assets from public to restricted, and add or change the time-limited access dates or times without changing the asset's URL in any way. This means that your developers don't need to change the URLs in their code when the access settings for that asset change.
To view or modify access control settings:
asset_control feature is enabled for your account, you can open the access control settings dialog box (shown above) by clicking the Public / Restricted access control button in one of the following locations:
- The Summary tab of the Media Library Preview pane
- The Asset Management Summary tab
From the dialog box that opens, you can view or change the access control mode between public and restricted, or adjust the time-limited access for restricted assets.
If the same access control settings need to be applied to a set of assets being uploaded to the Media Library, you can configure upload preset(s) with the desired restrictions. Set the upload preset(s) as the default Media Library upload presets, and the required access control settings will be automatically applied to the assets being uploaded.
If you don't want to set the upload preset(s) as the default Media Library upload preset(s), users may be able to apply restricted access control settings by uploading assets via the Media Library Upload Widget and selecting the Upload Preset with the desired settings.
It’s sometimes important to moderate assets uploaded to Cloudinary. For example, you might want to keep out inappropriate or offensive content, reject assets that don't answer your needs (e.g., making sure there are visible faces in profile images), or make sure that photos are of high enough quality.
Assets can be sent to moderation, both via the UI and programmatically, as part of the upload flow. In the UI, use upload presets to mark assets for moderation. For more information on programmatically marking assets for moderation on upload, see Moderation of uploaded assets.
There are different types of moderation that you can apply to your incoming assets:
- Automatic moderation: You can subscribe to a variety of add-ons that provide different automatic moderation functionality:
- Webpurify: Human moderation experts reject adult-oriented or inappropriate images.
- OPSWAT Metadefender: Detects and prevents advanced threats by incorporating multi-scanning and controlled data workflows.
- Amazon Rekognition: Rejects images with adult-oriented or inappropriate content using deep learning algorithms.
- Amazon Rekognition (Video) and Google Video Moderation: Reject videos with adult-oriented or inappropriate content using deep learning algorithms.
- Manual moderation: A Cloudinary moderator must personally review, and accept or reject, assets marked for manual moderation from the Moderation page. From there, the moderator can actually review all assets marked for moderation, per moderation type and status, and override a decision made by any one of the automatic moderations.
When an asset is sent for moderation, it's marked as Pending as soon as it's uploaded. Depending on the asset and the moderation type, the moderation process may be nearly instantaneous, or it may take some time. For example, it may take some processing time to automatically moderate large videos, whereas moderating an average-sized image is almost immediate when using algorithm based add-ons.
You can send incoming assets to be moderated automatically or manually.
To mark assets being uploaded for moderation:
- If you're marking an asset for automatic moderation, you must first subscribe to a moderation add-on.
Click Add-ons from the top navigation menu to view the and subscribe to the add-on you want to use.
- Create an upload preset and select the moderation offered by the add-on you subscribed to.
- There are two ways to apply the moderation to assets being uploaded: Apply the moderation automatically to all the assets uploaded to the Media Library by setting the upload preset with the desired moderation settings as the Media Library upload preset. ORChoose if you want to apply the moderation to assets during each upload. To apply the moderation, upload assets via the Media Library Upload Widget and select the Upload Preset with the desired moderation settings from the Advanced drop-down.NoteDepending on your setup, the Upload Presets option may not be available in the Advanced options of the Media Library Upload Widget. If it isn't available in your account's upload widget, you can submit a support request to activate it.
Once manual moderation is set up, assets that are uploaded are marked Pending and are sent to a moderation queue. A moderator is responsible for reviewing the pending assets, and accepting or rejecting them based on the appropriateness of the content.
From this page, you can also view all assets marked for any type of moderation, per moderation type and status. As the decisions made by automatic moderation add-ons are based on advanced algorithms, in some cases you may want to manually override the moderation decision and either approve a previously rejected image or reject an approved one. You can always manually override any decision that was made automatically. If you approve or reject an asset manually, the asset will be considered manually moderated, regardless which automatic moderation it was marked for, and it will be displayed when the Manual filter is selected.
Users with Master admin, Media Library admin, and Technical admin roles can moderate assets. Media Library users with Moderate asset administrator permissions can moderate assets in the folders they have Can edit or Can manage permissions to.
To review assets:
- Open the moderation page by selecting Moderation in the Media Library navigation pane.
- Browse the assets. You can select the moderation type and status of the assets you want to review.
- Decide to accept or reject them.
You can subscribe to a variety of add-ons that offer unique image and/or video processing or delivery capabilities, including celebrity recognition, automatic tagging, background removal, and asset moderation. Some of these add-ons are based on advanced Cloudinary AI functionality and others provide special functionality from a variety of vision and media processing partners. The add-ons are simple to use and fully integrated into Cloudinary's image and video management pipeline.
You can see a full list of the add-ons that you can subscribe to and decide which ones best suit your needs.
To subscribe to add-ons:
- Click to view the Available add-ons.
- Click add-ons to view their cards and read their descriptions.
- Once you've chosen the add-on you want, from its card, select a free or a paid plan to subscribe. Make sure the plan you select has the capacity to handle your expected volume.
You can apply add-on functionality to assets during uploads using upload presets. For example, you can set automatic tagging or background removal for all assets uploaded using a specific upload preset.
In addition, users can apply add-on functionality to assets that are already in the Media Library from the Analysis tab of the Manage page.
See an auto-tagging add-on in action from the Analysis tab of the Manage page: