Glossary

A finished piece of content produced from a template with specific content filled in, such as a localised banner or a print-ready poster.

An adaptation is a type of asset, distinguished by the fact that it was generated from a template.

Not to be confused with Adaptation Studio, the Storyteq CMP module used to produce adaptations.

Any managed digital file, such as an image, video, or document, together with its metadata.

Assets are stored, classified, and governed in the DAM, and distributed to users through portals.

A flexible, user-curated grouping of assets brought together for a purpose, without moving them from where they are stored.

A collection might gather the assets for a campaign or a brand area, for example.

Adding or removing an asset from a collection does not change where the asset itself lives.

Output transforms are downloadable (such as Storyteq outputs and high-res JPEGs).

Preview transforms (such as audio previews and video previews) generate lightweight versions and are not available for download.

A set of rules that controls which assets appear on a portal page, showing only the assets that meet its conditions and updating automatically as assets change.

A lens is a pre-filtered asset page, built from keyword rules that surface a relevant set of assets based on the keywords applied to assets, the asset type, and status.

A lens filters assets rather than copying or moving them, so the same asset can appear through several different lenses.

The structured information attached to an asset, such as fields, descriptions, and classification, that makes it findable and reusable.

Well-maintained metadata is what lets users search, filter, and retrieve the right assets.

A field in a template that you fill in to produce an adaptation, such as a headline, a price, or an image.

A template’s parameters define what you can change when you produce an adaptation; everything else stays fixed and on-brand. When you produce adaptations in a batch, each column in the spreadsheet is a parameter and each row is one set of parameter values.

Routes link the process, supplier, and transform together.

On a practical level, the route provides the order selection and order modal functionality.

The structured system of categories and values used to classify and filter assets.

Taxonomy lets users browse and find assets by dimensions such as brand, campaign, region, or channel.

A taxonomy has two levels:

Administrators govern taxonomy terms; end users do not create them ad hoc.

A reusable, parameterised design from which content variations are produced.

A designer builds the template once, with fixed brand elements and defined variable parameters. Users then generate branded content from it without designing each asset individually.

A group of content variations produced together from a single template.

For example, a batch might generate one version of an advert for each market or product in a list.

The area of a portal where the adaptations you produce are collected, ready to track, download, and share.

Adaptations you create from templates are placed in My Content, where you can follow their progress as they render. In some portals this area is also labelled User Adaptations.

Making content available for use, such as a finished asset appearing in a portal.

Publishing can also make a template available for users to build from.

Where reviewers annotate, comment on, and approve or reject the content in a review.

Review Studio opens when you launch a review, or select Go to Review in a review invitation. Reviewers annotate the content and add comments there, and the review’s decision makers approve or reject each item. Review Studio also lets you compare versions of an asset.

A defined sequence of stages that content moves through, such as briefing, review, approval, and publishing.

Workflows make content production repeatable and governed, with the right people involved at each stage.

The Storyteq CMP module for producing brand-compliant content from governed templates, across digital and print channels.

Adaptation Studio lets local teams create on-brand content from approved templates, without designer involvement for each asset.

An optional, separately priced extension bought on top of a module to add capability or raise a usage limit.

The Storyteq CMP module for briefing, producing, reviewing, and approving content through to publication.

Collaboration Hub connects marketing teams with agencies or internal studios, and moves work through a defined production workflow.

The Storyteq CMP module that gives teams a branded, self-service interface for finding and downloading approved brand assets.

Content Portal is the consumption layer of the DAM, the part users interact with, while the DAM administration layer sits behind it.

In the wider industry, this kind of interface is known as a brand portal.

A packageable unit of capability within a product.

In Storyteq CMP, the modules are Content Portal, Adaptation Studio, and Collaboration Hub.

Notifications sent to an external system in near real time when assets are created, edited, deleted, or versioned.

Rather than repeatedly polling CMP for updates, a subscribed endpoint receives automatic notifications.

This makes the service well suited to synchronising assets with other platforms, triggering downstream workflows, or maintaining audit logs.

A set of users managed together, used to grant access and roles to many people at once.

Storyteq’s service that lets users sign in to external integrations with their existing company credentials, routing each user to the correct identity provider.

The Identity Broker supports external integrations such as the CMP Asset Picker, including sign-in with single sign-on.

It sits between the integration and your identity provider, routing each user to the correct sign-in provider automatically, so the integration never handles their credentials.

Your organisation’s system, such as Azure AD, Okta, or Google Workspace, that authenticates users and confirms their identity to Storyteq.

Storyteq connects to your identity provider to enable single sign-on.

A configured, branded interface that gives a specific audience tailored access to assets and tools.

A portal serves a specific audience, such as a team, region, or partner.

Each portal can be configured with its own branding, permissions, and functionality to suit that audience.

A named level of access that determines what a user can do in the platform.

Roles are assigned to users directly or through groups.

Single sign-on: signing in once with your organisation’s identity provider to access Storyteq without separate credentials.

Storyteq CMP, the content marketing platform for planning, producing, managing, and distributing marketing content.

CMP stands for content marketing platform, which is also the industry category the product belongs to.

Storyteq’s platform for building master templates and producing large volumes of brand-consistent content at scale.

Creative Automation (CA) produces content variations across formats, sizes, languages, and channels.

Within Storyteq CMP, the equivalent capability is delivered by the Adaptation Studio module.

Creative automation is also the general industry term for this kind of template-based content production.

Digital asset management: the system for storing, organising, and distributing your brand’s digital assets.

In Storyteq CMP, the DAM has two sides:

Digital asset management is also the established industry term for this category of software.

The administration interface for LUMA, used by implementation teams to configure domains, asset types, taxonomy, workflows, and system settings.

LUMA Admin is where implementation teams configure LUMA, the platform Storyteq CMP is built on. It covers domain management, asset types, taxonomy, workflow configuration, and system settings. It isn’t available to customer users.

Storyteq’s application platform: the back end that stores, transforms, and distributes assets for Storyteq CMP and its portals.

LUMA is the application platform that Storyteq CMP is built on. It handles authentication, asset management, workflows, and the services that decide what each user can do. Users don’t work in LUMA directly: they reach its capabilities through Storyteq CMP and its portals, and implementers configure it through LUMA Admin.