Breadcrumbs

Publish content

Publish content

Publishing pushes your current document state from Activator to your connected repository (DAM), such as Veeva Vault or Aprimo. Publishing is the step that makes your work available downstream for review, distribution, and use in other systems.

This article covers how publishing works for:

  • Emails

  • Slides

  • Presentations (containers for slides)

Varies by tenant (Anthill-managed)
Button labels, required metadata, available renditions, and publish rules depend on tenant configuration and DAM type.

Before you publish

Do these checks first:

  • Save your latest edits

  • Preview the document (layout, links, interactions)

  • Ensure mandatory metadata is completed (if your tenant enforces it)

  • For Slides: ensure the right slides are included and ordered in the Presentation

Publish an Email

Emails are published directly from the document editor.

Steps

  1. Open the Email document in the Editor

  2. Click Publish to Vault/Aprimo (top right)

  3. Fill in metadata if prompted

  4. Select rendition options (if prompted)

    • Example: Visual representation vs MLR report (optional feature)

  5. Click Publish again to confirm

  6. Wait for the success confirmation

GIF - Publish Email-20260218-081540.gif

What happens when you publish an Email

  • Activator generates the final email output and sends it to the DAM according to tenant mapping rules

  • A new published version is created in the DAM

Publish a Slide

Slides typically live inside a Presentation, but the Slide itself can have its own publish state.

How to recognise an unpublished Slide

New Slides often show an indicator such as “Not in Vault/Aprimo”. This remains until the Slide has been published at least once.

Steps

  1. Open the Slide

  2. Make your edits

  3. Click Publish

  4. Wait for confirmation and verify the unpublished indicator is removed

image-20250930-121615.png
image-20250930-122003.png

Notes

  • Publishing a Slide updates the Slide record/version in the DAM.

  • Publishing a Slide does not necessarily update the Presentation container (see next section).

Publish a Presentation

A Presentation represents the package/structure: slide membership, ordering, and (in many setups) the deliverable that iPad/CRM experiences depend on. Even if individual Slides are published, you often still need to publish the Presentation to push structural changes.

When you must publish the Presentation

  • You added Slides to the Presentation

  • You removed Slides from the Presentation

  • You reordered Slides

  • Your tenant uses Presentation publish to generate/update a downstream package

Steps

  1. Open the Presentation

  2. Click Publish to Vault/Aprimo

  3. If prompted, review the wizard:

    • You may be offered to publish any unpublished Slides as part of the flow

  4. Confirm and wait for success

GIF - Publish Presentation-20260218-093150.gif

What happens when you publish a Presentation

  • The Presentation package (membership/order and any required artefacts) is updated in the DAM

  • Depending on tenant configuration, it may update references used downstream by CRM/viewers

Unpublished changes (retention)

Activator retains unpublished changes for up to 90 days, but you should publish regularly while working—especially before handover, review, or downstream testing.

Practical rule

  • Publish after meaningful milestones (e.g., “draft ready”, “ready for review”, “final ready for distribution”)

  • Don’t let work sit unpublished close to the retention window

Common publish issues

“Publish is blocked”

Typical causes:

  • Missing mandatory metadata

  • Permissions/role restrictions

  • DAM connectivity or validation errors

“Slide is published but Presentation isn’t updated”

You likely changed membership/order. Publish the Presentation to push those changes.

“Published output doesn’t match what I expected”

Typical causes:

  • Changes were not saved before publish

  • Wrong rendition selected (if applicable)

  • Asset rendition differences from DAM