Portal
Managing your services

Managing your services

⚠️

This documentation describes a future version of the platform.

Most of what you do in the portal is creating or administering content.

There are a number of configuration settings that determine how the platform processes the assets you add and the IIIF Manifests you create, as well as account and billing settings.

Creating an account

Visit iiif-cloud.digirati.com/signup (opens in a new tab). You will need to provide contact information and billing information (e.g., credit card details).

You can start with a trial account which has no costs for the first year but is limited to a certain amount of storage and bandwidth use. You can also set a limit on billing, to avoid unexpected costs. You can cancel your account at any time, there is no minimum term.

If you add more content or use more bandwidth than the free tier allows, you will start incurring charges, which are billed monthly, up to any configured billing limit.

Once you have signed up, you can immediately start making IIIF Manifests and generating IIIF Image Services from your images, as well as AV content. If you have images or other assets waiting to turn into IIIF, take a look at the Quick Start.

Viewing your billing information

Billing is broken down by:

  • How much storage your assets and their derivatives use
  • How much bandwidth is consumed by web visitors viewing your assets and derivatives
  • processing costs to produce derivatives from pipelines (e.g., OCR)
  • There is no cost for storing IIIF Manifests and Collections, up to a high limit (currently 10,000): you are billed for assets served by the platform (image services, AV derivatives etc)

You can see your previous charges (if any) and current billing information in the portal at Billing.

Extra charges apply for access-controlled resources (see Restricting access to assets for details).

Reporting

Reporting

This page gives you a breakdown of:

  • How much storage you are using
  • How many assets you have registered, showing distribution by type and by delivery channel.
  • How many IIIF Manifests you have created
  • How many IIIF Collections you have created
  • How many views you have had of your manifests and assets within them

Adding new users

Portal Users

You can add new portal users in addition to the one you created at signup. You need to provide email addresses and display name. You can also create a signup link that you can send to your users to allow them to perform this step themselves (recommended). Otherwise they will need to set a password on first use.

See also Advanced Administration for controlling user permissions.

Managing API Clients

Client IDs and Secrets

If you want to use the IIIF Cloud Services API (for example, building IIIF or registering assets in your own workflows) you will need to register client applications. You can view registered API clients here and manage their credentials.

IIIF Presentation API settings

Default language for labels

When creating Manifests and Collections, you supply a single string for the label. Later, you can add more strings, in multiple languages. The default language setting determines what language this initial label is assumed to be.

Manifest Identity

When creating IIIF Manifests, you can use their hierarchical path within the storage as their canonical URI:

https://dlcs.io/iiif/some-path/with-slugs/to-manifest (opens in a new tab)

...or you can use a "flat" identity, using the assigned Manifest ID:

https://dlcs.io/iiif/manifests/we456fga (opens in a new tab)

When creating folders for storage, IIIF Collections, and IIIF Manifests within folders or Collections, you can specify a "slug" - the path element in the URI.

Both forms of URI will be resolved by the platform, but one will redirect to the other depending on which you choose to be the "canonical" form. This will be the one declared in the Manifest's id property.

The following slugs are reserved at the top level, you can't use them as top level storage folders, or names of manifests in the root, or collections in the root:

  • manifests
  • collections
  • canvases

Canvases are always used in the https://dlcs.io/iiif/canvases/fr5tgh7a (opens in a new tab) form if created by the API.

touched 2025-09-23T12:04:54