Marmind - Censhare Integration

📄 Summary: What You’ll Learn in This Article

This article explains how the Marmind - Censhare integration enables streamlined digital asset management by connecting Marmind’s marketing workflows with Censhare’s centralized DAM system.

• Overview of Key Functionalities

• Prerequisites

🧑‍🤝‍🧑 Who Should Read This?

This article is most useful for anyone who works with assets in Marmind when Censhare is connected: marketing teams, campaign managers, product owners and digital asset managers.

✔️ Prerequisites: What Should You Know Before Getting Started?

Introduction to the Marmind - Censhare Integration

How the integration works

The integration connects Marmind’s campaign planning with Censhare as your Digital Asset Management (DAM) system. It enables seamless asset usage in marketing workflows while maintaining a single source of truth in Censhare. It works on two levels:

• Planning structure (tree objects): Your Marmind structure, meaning workspaces, campaigns, channels, actions and work packages, is represented in Censhare as linked tree object assets. Censhare users can browse this structure and work in the context of your campaigns without leaving Censhare.

• Media assets: Files such as images, videos and documents are stored in Censhare as media assets and referenced in Marmind. You can upload files from Marmind directly to Censhare, use existing Censhare assets in Marmind, and keep shared metadata in sync between both systems.

The two levels are connected. When you add a media asset to a Marmind object (for example a campaign), that object and its parent objects are created in Censhare automatically, if they don’t exist there yet. Only the direct path up to the organization root is created. You can also create an object in Censhare yourself with Create in Censhare.

Key Principles

• Media Assets (Files) live in Censhare. Marmind shows a reference to each Censhare asset. Deleting an asset in Marmind deletes only the reference.

• One asset, many places. The same Censhare asset can be used in several campaigns or objects in Marmind. Changes to the file or its shared metadata apply everywhere it is used.

• Changes sync automatically. Asset names, versions, relations, statuses and mapped metadata are kept in sync between both systems.

• Two statuses, one per system. Media assets and tree objects each have a Censhare status and a Marmind status. Each status is managed in its own system and shown read-only in the other.

  • Tree objects: the two statuses are independent. You set the Marmind status in Marmind and the Censhare status in Censhare, manually or through a workflow.

  • Media assets: the Censhare status comes from the Censhare workflow. The Marmind status reflects the approval to use the asset in a specific Marmind object. It can only be changed after the Censhare workflow reaches a final approved status.

• Deeplinking: One-click access from Marmind to the corresponding asset in Censhare and vice versa is available via the “Open in Censhare” or “Open in Marmind” actions.

Access & Permissions

• Single Sign-On (SSO): Uses Censhare's Keycloak for authentication. One login grants access to both platforms. Single-log out (SLO) enables you to log-out from both systems simultaneously.

• Permissions:

  • Assets permissions are based on Censhare's domain system. Users can only act within their assigned domains. Users without Censhare permissions are restricted from asset operations, except for viewing asset containers in Marmind — and only if they have view asset permissions. In this case the asset preview will be shown with a blocked placeholder image but the asset name will be visible.

❓ FAQs