📄 Summary: What You’ll Learn in This Article
This article explains how your Marmind planning structure (workspaces, campaigns and so on) appears in Censhare and stays in sync.
-
How Marmind objects are created in Censhare
-
What is synced and where you can edit it
-
How the Marmind status and the Censhare status work for objects
-
What happens when you delete an object
-
What Censhare users see
🧑‍🤝‍🧑 Who Should Read This?
This article is most useful for:
-
Marmind users who plan campaigns and work with assets when Censhare is connected.
-
Censhare users who work with media assets that belong to Marmind campaigns.
✔️ Prerequisites: What Should You Know Before Getting Started?
Level: Intermediate
Access required: Your company uses the Marmind – Censhare connector.
-
To get the most out of this article, readers should have basic familiarity with Marmind and Censhare and be able to navigate both systems.
Key Points
-
Your Marmind structure is mirrored in Censhare. Each Marmind object becomes a tree object asset in Censhare, with the same parent-child structure.
-
Marmind is the leading system for objects. You edit objects in Marmind. In Censhare they are read-only.
-
Each object has two independent statuses. The Marmind status is set in Marmind, the Censhare status in Censhare. Each one is shown read-only in the other system.
What Are Tree Objects?
Tree objects are the planning objects that make up your Marmind structure:
Organization root → Workspace → Campaign → Channel → Action → Work package
In Censhare, each of these objects is stored as a tree object asset. Censhare users can then:
-
browse your Marmind structure
-
see which media assets belong to which campaign or other object
-
assign media assets to Marmind objects
How Objects Get into Censhare
Marmind objects can be created in Censhare in three ways.
Option 1: Create It Yourself
-
Open the object in Marmind (for example a campaign).
-
Click Create in Censhare in the object header.
The object is created in Censhare, together with all its parent objects up to the organization root, unless they already exist there.
After that, the Create in Censhare button is replaced by the Censhare logo. Click it to open the object in Censhare in a new tab.
Option 2: Automatically, When You Add an Asset
When you upload or add a media asset to an object, that object and its parent objects are created in Censhare automatically. You don’t need to click Create in Censhare first.
Only the direct path from the object up to the organization root is created. Other objects in the same workspace are not.
Example: You upload an asset to the campaign Global Summer Campaign, which sits in the workspace path ENTIRELY – END2END DEMO → RETAIL → EMEA → DE.
Censhare receives the asset, the campaign and the four workspaces above it, with the same parent-child relations.
Other workspaces under EMEA, such as UK, BE, FR or NL, are not created.
Option 3: Created in Bulk by Your Admin
Your admin can create a whole part of your Marmind structure in Censhare at once. For example, a workspace with all its campaigns, channels, actions and work packages, including objects that don’t have any assets yet.
During this step, your admin can also link Marmind objects to assets that already exist in Censhare, so no new tree object assets are created for them. Those Censhare assets must have an asset type that is allowed for Marmind tree objects.
Contact your admin if you want a part of your structure to be available in Censhare before any assets are added.
Which Censhare Asset Type Is Used
The asset type an object gets in Censhare depends on its object type and category:
-
Default: Each object type is created as its own Marmind asset type. For example, a campaign becomes a Marmind Campaign asset.
-
Mapped category: Your admin can link a category of a workspace, campaign or action to one of your company’s own Censhare asset types. Every object with that type and category is then created with this asset type instead of the default. Several categories can share the same asset type.
Good to know:
-
Channels always use the default asset type.
-
Once an object exists in Censhare, you can no longer change its category in Marmind, because the category decides the asset type.
Open an Object in the Other System
|
From |
Action |
Opens |
|---|---|---|
|
Marmind |
Censhare logo in the object header (shown once the object exists in Censhare) |
The tree object asset in Censhare, in a new tab |
|
Censhare |
Open in Marmind |
The object’s details in Marmind, in a new tab |
What Is Synced
Marmind is the leading system for objects. Changes made in Marmind are sent to Censhare automatically.
|
Information |
Edit in |
Shown in Censhare |
|---|---|---|
|
Name |
Marmind |
Yes, read-only |
|
Marmind number |
— |
Yes, read-only |
|
Marmind ID |
— |
Yes, read-only |
|
Marmind type |
— |
Yes, read-only |
|
Marmind status |
Marmind |
Yes, read-only |
|
Custom fields mapped to Censhare (if configured) |
Marmind |
Yes, read-only |
Good to know:
-
Renaming or moving an object in Marmind updates it in Censhare automatically.
-
The category is locked once the object exists in Censhare. You can no longer change it in Marmind.
-
Changes from automations in Censhare are kept in sync. Object fields can’t be edited in the Censhare UI. If they are changed through an API, automation or another integration in Censhare, the change is synced back to Marmind as a safeguard so both systems match.
Object Status
Each tree object has two statuses. They are independent: changing one doesn’t affect the other.
|
Status |
Set in |
Shown in the other system |
|---|---|---|
|
Marmind status |
Marmind |
Censhare, read-only |
|
Censhare status |
Censhare |
Marmind, read-only, next to the Marmind status. |
-
Each status can be changed manually or by a workflow in its own system. The change appears in the other system automatically.
-
The Censhare status is hidden in Marmind until a status step has been set for the object in Censhare.
Note: Media assets work differently. For media assets, the Marmind status stays locked until the Censhare workflow reaches a final status. See Censhare Integration: Working with Assets → Asset Status and Approval.
Delete an Object
When you delete an object in Marmind:
-
the tree object asset is also deleted in Censhare, together with its link to its parent object
-
media assets that were assigned to the object stay in Censhare. Only their link to the deleted object is removed.
Objects can’t be deleted from Censhare. Delete them in Marmind.
What Censhare Users See
In Censhare, your Marmind structure appears as linked tree object assets. By default they are stored in the root.marmind-internal domain.
-
Read-only: The Marmind properties can’t be edited in Censhare. Object names, fields and parent-child relations are changed in Marmind and synced to Censhare automatically.
-
Statuses: The Marmind status is shown read-only. The Censhare status is set and managed in Censhare.
Tree Object Workspace
When you open a Marmind object in Censhare, you see these widgets:
|
Widget |
What it shows |
|---|---|
|
Assigned preview (if available) |
The object’s main picture from Marmind |
|
Marmind properties |
The object’s Marmind information: name, Marmind number, Marmind ID, Marmind type and Marmind status, plus any custom fields your company syncs |
|
Marmind objects |
The parent objects in the Marmind structure |
|
Related media |
All media assets assigned to this object |
|
Status |
The object’s Censhare status |
Click Open in Marmind to open the object in Marmind in a new browser tab.
âť“ FAQs