Step-by-step guide for integrating MASV with your Iconik system
This article includes the following topics:
Creating Application IDs and Tokens in Iconik
How to connect Iconik with MASV
How the MASV and Iconik integration works
Iconik storage account requirements
Overview
Iconik is a Multimedia Asset Management (MAM) tool that can be used to gather and organize media from anywhere. When connected to your MASV Portal(s), you can receive large media files from anyone, anywhere at blazing fast speeds and have them delivered directly to your Iconik account. You can also collect metadata from a Portal and flow it through to Iconik.
These instructions assume that you have selected and configured storage for Iconik. For more information, see the Iconik Help and Iconik storage account requirements.
Creating Application IDs and Tokens in Iconik
First, you need an Iconik account that is connected to your cloud storage provider of choice (Azure, Backblaze B2, Google Cloud Storage, or AWS S3). From your Iconik workspace, you can create and copy an Application Token and Application ID.
Note: You need to have permission in Iconik to create tokens. Please contact your Iconik administrator if you need access.
How to create an Application Token and ID in Iconik
-
Log in to your Iconik account.
-
Select the Admin button at the top of the page.
-
From the sidebar on the left, select Settings > Application Tokens.
-
Select + New Application in the upper right corner. The Add a new application window opens.
-
In the Name box, enter a meaningful name, such as the name of the application (MASV) and any other identifying information in case you create more than connection for the application.
-
From the User drop-down menu, select a user who has the necessary authorization for the token. For example, they must have read, write, and delete authorization to upload files to your storage account, create jobs, initiate transcode operations, and must be a Power user. For more information, see Iconik groups and roles.
-
Select the Create button to close the window.
-
On the Application Tokens page, in the Name column, find the connection you created, and select the corresponding Create New button in the Tokens column.
-
Copy and save both of the following in a secure place. Both are required to connect MASV.
-
Select the button beside Copy Token to copy the Application Token and save it.
-
Select the button in the corresponding ID column to copy the Application ID and save it.
-
Iconik groups and roles
The user that the application token is associated with must belong to a group with specific roles enabled OR be an Admin user to ensure that MASV has the necessary access to transfer your files. They must be a Power user to ensure that package metadata can be added to each asset.
How to configure an Iconik group for a MASV connection
- Log in to your Iconik account.
- Select the Admin button at the top of the page.

-
From the sidebar on the left, select the Groups.
-
On the Groups page, in the Name column, select the group you want. If you need to create a new group, please refer to the Iconik Help.
-
In the Group Information area, enable the Roles Advanced view toggle.
-
Verify that the following permissions are enabled, expanding each list item as required. (others permissions can be enabled too, these are the minimum):
-
Assets: create, delete, purge, write
-
Collections: create, delete, purge, read, write
-
Files: delete, purge, read, write
-
Formats: create, write
-
Jobs: delete, write
-
Metadata fields: read, write
-
Metadata views: read, write
-
Storages: read
-
Transcode jobs: create
-
-
Select Update in the lower right corner to apply any changes.
How to connect Iconik with MASV
-
In the MASV Web App, as an account Owner, Admin, or Integration Manager (roles), select Integrations from the sidebar on the left.
-
On the Integrations page, select the Available Integrations tab, and select Iconik.
-
In the Add Integration window, paste in the App ID (Application ID) and App Token (Application ID) that you created and copied from Iconik.
-
Select the Verify button to confirm the connection between MASV and Iconik.
-
From the Choose an Account drop-down list, select the storage where MASV will save files.
-
(Optional) If you want to set a specific subdirectory, enter a Target Directory.
- To transfer metadata to your MAM, enable the Sync Metadata with Media Asset Manager checkbox. For more information, see Getting and Integrating Metadata.
-
Select Connect to save your settings.
-
To verify the connection, on the Integrations page, select the My Integrations tab, refresh the page, and confirm that Iconik appears in the integrations list with Status indicating OK.
Note: MASV requires read, write and delete permissions on the storage account. If the storage you want to use does not appear in this list, please see Iconik storage account requirements.
That's it! After authentication, the service is connected with MASV. You can now:
How the MASV and Iconik integration works
When a package is uploaded to a connected MASV Portal or the Send to Cloud feature is used from the package list, MASV transfers the package to Iconik and the connected storage account.
-
In MASV:
-
Portal recipients receive an email with a download link as well as a second email indicating the status of the transfer to Iconik
-
A message is published to a connected Slack channel to indicate the transfer status to Iconik
-
-
In Iconik:
-
A collection is created and named for the package, with each file organized within it.
-
Send to cloud: /MASV/[package name]
-
Received portal uploads: /Portal Downloads/[portal name]/[package name]
-
-
The package structure is replicated, with each folder being represented as a collection.
-
A job is created for each file so that you can monitor the progress within Iconik’s Admin panel if you wish.
-
Each file has a keyframe (preview thumbnail) generated for it automatically.
-
The package name, uploader’s email address, and portal name (if received via portal) is attached to the description field of each file asset.
-
-
In the cloud storage account:
-
A directory is created and named for the package, with each file organized within it.
-
Send to cloud: /MASV/[package name]
-
Received portal uploads: /Portal Downloads/[portal name]/[package name]
-
-
The package file and folder structure is replicated as-is.
-
Note: Empty subdirectories are not recreated in Iconik or the cloud storage account.
Iconik storage account requirements
MASV uploads packages to the storage that your Iconik account is already connected to. For transfers to work correctly, there are a few requirements that must be met.
If the cloud storage service does not appear as an option when integrating Iconik with MASV, review the information below carefully to ensure permissions and settings are correct.
Note: We recommend that you upload a file from within Iconik to ensure the storage connection is working properly.
Required settings
- Purpose: Files
- Method: (Backblaze) B2, AZURE, (Google Cloud Storage) GCS, S3 (AWS or compatible)
- Status: Active
- Read: Enabled
- Write: Enabled
- Delete: Enabled
Optional settings
-
Path: A path may be specified or left empty. MASV will create directories to hold each package
- Send to cloud: /MASV/[package name]
- Received portal uploads: /Portal Downloads/[portal name]/[package name]
- Setting a path on your storage configuration will result in the above directories being created within that path. For example, if your path was set to “/uploads” then packages would be transferred to /uploads/MASV/[package name] and /uploads/Portal Downloads/[portal name]/[package name]
-
Add unique id to the filenames: If this is enabled the filenames in connected storage will have a unique identifier appended to their names. This will not appear in Iconik itself.
Note: MASV attempts to identify if a package was uploaded previously and avoids overwriting by appending a number to the end of the package name. This is reflected in Iconik and the cloud storage. Example: My Upload (2)
-
ACLs
-
Ensure that the user to whom the application belongs has at least read, write, and delete access on the storage account.
-
- Other storage settings do not affect MASV behaviour
Note: If you change cloud storage services for your Iconik account, it is best to delete your current MASV integration and reconnect.
Troubleshooting
For any and all issues related to upload errors, the key debugging steps are:
- Can the user associated with the application token upload to the storage account within Iconik? For example, can they log in to Iconik, go to Upload, select the storage account, and upload a single file? If not, check the following:
- Verify the Group Roles for the user.
- Verify the storage account configuration.
- In MASV, re-enter the App ID and App Token in the Add a Cloud Connection window when integrating Iconik, save, then retry the job. MASV will detect if there are any issues with the credentials.
Google Cloud Storage (GCS)
Backblaze (B2)
Azure
S3 (AWS S3 or S3 compatible storage)
- Iconik setup instructions (AWS S3)
- Iconik setup instructions (S3 Compatible)