Appearance
Workflows
A Workflow (called a Workflow configuration in Relayter) defines the production process a Publication's items follow — from briefing, through layout and review, to delivery. Workflows are managed under Workflow → Configurations, and every publication is bound to exactly one workflow configuration.
Steps
A workflow is made up of Steps (for example: Briefing, Layout, Review, Delivered). Each step defines which tools and actions are available to work on an item, and who can access it. You can create as many steps as you need for your workflow.
Each step specifies:
- Components (tools/tabs) available while an item is in that step — for example Briefing, Layout, Upload, Preview, Package management, or Sticky notes.
- Which roles can access it — a step can be restricted so only users whose role has the required permissions can see or act on items in that step.
- Deadline reminders (optional) — send notifications to specific roles, users, or email addresses before or after an item's deadline.
Components
Components are the tools and interfaces available within a step. They define what work can be done on an item. Common components include:
- Overview — displays publication items in a grid, with options to arrange pages or move items through transitions.
- Briefing — shows and allows assignment of briefing (campaign) items to publication items.
- Layout — allows editing of the item's design and content.
- Preview — displays the item's rendered output and allows review before delivery.
- Package Management — lets users add items to or remove items from packages.
- Upload — allows uploading files to the item.
- Upload Assets — allows uploading assets linked to the item.
- Sticky Notes — displays sticky notes for collaboration and issue tracking.
- Automation — shows applicable workflow automations that can be triggered.
- Assets — displays assets available to add to the item.
- Add Pages — allows adding additional pages to the item during design.
- List View — displays items in a customizable list with filterable columns.
Actions
Within a step, individual actions can have their own permission requirements. Actions are specific operations that users can perform on an item or its components — such as signing off, uploading files, downloading, editing, assigning briefing items, or managing sticky notes. This gives fine-grained control over exactly what each role can do at each stage — not just which steps they can see.
Common actions include:
- Sign Off — approve or reject an item.
- Download — download item files or assets.
- Edit — modify item details, tags, or template settings.
- Assign — assign briefing items to the publication item.
- Add to Package — include the item in a package for export.
Transitions
A Transition moves a Publication Item from one step to another. Transitions can:
- Happen automatically when a condition is met, or require a user to manually trigger them.
- Run a set of automated tasks when they fire — for example generating items, updating layout content, sending notifications, creating export packages, or removing existing sign-off approvals.
- Be flagged as destructive (for example, deleting publication items or removing files) — Relayter shows a confirmation dialog before running destructive transitions.
When a transition fires, it can execute "recipe tasks" — automated steps that happen behind the scenes, such as:
- Sending notifications to specific roles or email addresses.
- Generating new publication items from briefing (campaign) items.
- Creating or refreshing packages for export.
- Removing approvals or resetting sign-off statuses.
- Updating layout or file content.
- Deleting items or removing files (marked as destructive).
Workflow Automations
Separately from a workflow's steps and transitions, Workflow → Automations lets you automatically generate Publication Items from your campaign's Briefing during a workflow transition, instead of assigning Briefing content to items by hand.
An automation is made up of rules. Each rule defines:
- Conditions that Briefing (Campaign) items are checked against.
- A Template to use for the Publication Items it creates.
- Whether each matching Briefing item should get its own Publication Item, or all matches should be combined into a single Publication Item.
- Whether a Publication Item should still be created even when nothing matches the rule's conditions.
An automation's rules run when the automation is triggered from a workflow transition, so it fires automatically as items move through the steps your team has configured.