2026.1 2025.2 2025.1 2024.3 2024.2 2024.1 2023.1
2026.1 2025.2 2025.1 2024.3 2024.2 2024.1 2023.1
Breadcrumbs

Marmind integration

Prerequisites

This is a Cloud-only feature and subject to separate licensing.

  • You need to be on Censhare Cloud

  • You need to become a Marmind customer

Please reach out to your project manager to learn how to fulfil these requirements.

Steps to start with Marmind

Once the prerequisites are met, you need to:

  • Obtain the license.

  • Wait for the integration to be deployed.

  • Configure SSO (optional). By default, Censhare IT performs this configuration. For detailed instructions, see SSO integration and user management (Partner login required).

  • By default, Censhare IT enables the Marmind module in the Censhare Admin Client.

  • Configure the Marmind APIs (optional) as described below. Censhare IT performs this configuration by default.

Marmind module configuration in the Censhare Admin Client

Marmind integration comes pre-configured and enabled in the Censhare Admin Client. These default settings usually do not need to be changed, and we do not recommend changing them.

Public and Sync APIs

Marmind configuration can be found under:

Configuration → Modules → Entirely Integration → Marmind Integration (Public API)/(Sync API)

Some settings are currently the same as in the HCMS server module configuration, with the same logic behind.

The Marmind integration has two configurations, one for each API.

  • Public API acts on behalf of the user in the Marmind UI when browsing or adding assets as explained in Understanding the Marmind integration.

  • Sync API keeps data in sync between two systems when assets are edited.

The settings are identical except for the authentication method.

Public API requires authorization as a Censhare user and uses that user’s permissions. For example, it is used when a user browses Censhare assets in the Marmind UI to add them to a Marmind object.

Sync API uses a system user and enables a background synchronization. Changes made to assets in one system are propagated to the other system through this API.

Asset filter

By default, the integration uses only the current version of an asset. It is recommended to leave this filter as-is. Changing this filter may affect the integration logic, so plan any changes carefully.

The same applies to adding new filters. Filtering out checked-out assets is the only suitable use case we can think of; it may help prevent confusion when two users edit the same asset from different systems.

Placeholder asset conversion

Marmind placeholder assets, known internally as "marmind.media-placeholder", allow users to reserve an asset before its file is available.

When a user uploads a file to a placeholder asset, an asset attribute module converts it automatically to the correct asset type. This module is disabled by default.

To enable it:

  1. Open the Censhare Admin Client and navigate to:

    Configuration → Modules → Asset Attributes

  2. Select the Marmind: Convert media placeholder on upload module.

  3. Enable the checkbox in the module dialog.

By default, a placeholder asset converts into an Image, Video, Audio, or Document asset based on the MIME type of the uploaded file. You can customize this mapping in the same module dialog.

Known issues

Censhare Web has a known session-timeout issue: after 25 minutes of inactivity, it logs the user out. This issue also affects the behavior of the Marmind web client.

In the Marmind web client, after 25 minutes of inactivity while working with assets, you cannot perform actions on those assets. You can still use the rest of the Marmind interface. To resume working with the assets, log out and log in again.