Concepts Overview

Relayter helps marketing, brand, and production teams turn product data and creative assets into finished publications — from print catalogs to digital banners — through a configurable, trackable production process.

This page gives you a mental model of Relayter's core objects and how they fit together. Each object links to a dedicated concept article with more detail.

The building blocks

Products are the data records behind what you're promoting (for example, items in a catalog). Each product can have custom fields (price, description, SKU, etc.) and linked images.

Assets are the images, videos, and other files you work with. An asset can be linked to one or more Products, and used directly in a publication.

Campaigns group the work for a marketing initiative. A campaign has a Briefing — a list of content rows (each referencing Products and Assets) that describes what needs to be produced — and one or more Publications.

Projects are an alternative container for Publications, used when the work isn't organized around a campaign Briefing.

Publications are the actual outputs you're producing (for example, "Summer Catalog" or "Homepage Banners"). A publication belongs to a Campaign or a Project, and follows exactly one Workflow.

Publication Items are the individual pieces inside a publication — a single page, a spread, or a single digital asset — each generated from a Template and populated with content from the campaign's Briefing or with Assets directly.

Workflows define the steps a Publication Item moves through on its way to being finished (for example, Briefing → Layout → Review → Delivered), including who is allowed to work on each step and what happens automatically when an item moves between steps.

Templates are the reusable layouts (InDesign layouts, After Effects projects, or HTML projects) used to generate Publication Items.

How they relate

Product ──┐
          ├─▶ Campaign Item (briefing row) ──▶ Publication Item ──▶ generated using a Template
Asset ────┘                                          │
                                                      ▼
                                              moves through a Workflow
                                              (Steps and Transitions)

A Campaign holds the Briefing (its Campaign Items, each pointing at Products and/or Assets) and one or more Publications. Each Publication is bound to a Workflow and contains Publication Items. A Publication Item is built from a Template and filled with content from the Briefing (or directly with an Asset), then moves through the Workflow's steps — for example from layout, through review and sign-off, to final export.

Other concepts you'll encounter

• Briefings — the data behind your work. Campaign Briefings are lists of items you need to produce; Master Briefings are reusable templates.
• Data Fields and Forms — custom fields and the forms used to collect data for Briefings, Products, and Assets.
• Roles and permissions — control who in your team can see and do what.
• Content Groups and Content Rules — restrict which users can see or work with specific content, independent of their role.
• Variants — let a Campaign, Publication, or Template support more than one version of the same content (for example, different languages or markets).
• Packages — bundles of finished Publication Item files, created for export or delivery to another system, using an Export setup.
• Sticky notes — comments and proofing annotations left directly on a Publication Item's preview.
• Workflow Automations — rules that automatically generate Publication Items from a Briefing.
• Notifications — keep your team informed about work progress and workflow events.
• Static and Dynamic Content — the two approaches to creating and templating publication content.
• Rulesets — rules that determine what content appears in your output based on data conditions.
• Design Resources — shared fonts, design libraries, master pages, and project files used across templates.
• Asset Automation — automatically process and organize assets as they're ingested.
• Integrations — integrate Relayter with external systems and manage team access.
• Audit Trail — view a record of changes and actions taken in your team.