These are the roles that are needed:

  • Admin
  • Read storage
  • Write storage
  • Reindex storage


Adding Google Cloud Storage

Prepare for adding the storage.

If you are setting up a third party bucket we strongly recommend you read our knowledgebase article Controlling Costs as using iconik with third party buckets may cause costs for you.

To start with please ensure you have the following details ready to configure iconik with your Google Cloud Storage (your Google Cloud administrator should be able to provide these if you don't have them):

  • Service Account JSON - The Service account JSON for the Google Cloud Storage account that you wish to use.
  • Bucket - The name of the Google Cloud Storage bucket you wish to use.
  • Path - If left empty, iconik will use the whole bucket. Otherwise defines which part of the bucket the storage should start at.
  • Project - The Google Cloud Project name which the bucket resides.

Setup Permissions

The service account you are using need to have the following permissions to work correctly:


The easiest way to achieve this is to add the roles Storage Legacy Bucket Owner, and Storage Legacy Object Owner. Note that Bucket Owner is not enough on its own.

Where to add storage

  1. Click on ADMIN in the top navigation.
  2. Choose Storages from the left navigation bar.
  3. Click on + NEW STORAGE to open the form to create a storage.

iconik  storage configuration

Start filling out the parameters

  1. Choose the purpose for the storage.
    • Files - for general storage of files.
    • Keyframes - The storage stores only keyframes generated by iconik.
    • Proxies - The storage stores only proxies generated by iconik
    • Export - The storage is a destination for export jobs.
    • Archive - The storage is an archive destination
  2. Select **Google Cloud ** as the Storage Type
  3. Input your Service Account JSON, Bucket and Project as gathered in the preparation step to the fields.
  4. Optionally add a root Path if you don't want iconik to use the whole storage.
  5. Add unique id to the filenames - turn this on to avoid filename collisions. This setting will be inactive for archive storages - and the filename will be kept as it is on the source storage
  6. Select Read if you want iconik to be able to read files on the storage.
  7. Select Write if you want iconik to be able to write files to the storage.
  8. Select Delete if you would like iconik to have the ability to delete files on this storage. Please note, that if this is set to true, that when an asset is deleted in iconik it will also be removed from this storage when Purging
  9. Select Enable Scan if you wish to enable scanning for new files on this storage. A label "SCAN" will be visible next to the storage in the list. Click on SCAN to scan through the cloud storage and add the new files to iconik.
  10. If you only wish to scan a subset of the directories on this bucket, you can enter in Scan Directories which will limit the scanning to these directories only.
  11. Click to continue.

iconik will verify that is has access to the storage and report back if it finds that it doesn't have the necessary requirements or the credentials do not work.

Next steps

There are more parameters that can be configured, and these are detailed under: editing Google Cloud Storage

Learn more.