Skip to main content

​
Overview

Ownership controls who can see and change a record. You assign users as owners or followers of a record; a Journey Manager only sees the records they own or follow, and only owners can change them. For the mental model, see Core concepts.
Ownership only affects Journey Manager users. A super admin or Master bypasses ownership entirely — they see and can change every record, whoever owns it.
Ownership applies to many object types — Contacts, Organizations, Orders, Content Instances, Documents, Conversations, and more.

​
Where to find it

Each record has an ownership list where you add or remove its owners and followers.

​
Roles

RoleAccess
OwnerFull access — view, edit, and delete the record.
FollowerRead-only — the record shows up in their lists, but they can’t change it.

​
Properties

Each ownership entry describes one user’s relationship to the record:
PropertyTypeRequiredDescription
user_idreferenceYesThe user who owns or follows the record.
roleenumYesowner or follower.
email / given_name / last_namestringAutoThe user’s details, filled in and kept in sync automatically.

​
Default ownership

Templates and Profiles can set a default ownership that new records inherit. When a record is created, its owners and followers start from those defaults, and the Journey Manager who creates it is automatically added as an owner.

​
Document ownership modes

A Document Template chooses how its documents get their ownership:
  • Independent (default) — a document’s ownership comes from the template’s default ownership plus its Journey Manager creator, and you edit it directly.
  • Sync with contact — a document copies its parent Contact’s ownership and stays in sync: you can’t edit it directly, and changes to the Contact’s ownership propagate to its documents.

​
Behaviour & rules

  • Journey Manager users see only their records. A JM’s lists are filtered to the records they own or follow. A super admin or Master bypasses this and sees everything.
  • Only owners can change a record. For a JM, updating or deleting a record requires being an owner; followers are read-only. Super admins and Masters can change any record.
  • Creators become owners. A Journey Manager who creates a record is added as an owner automatically.
  • Owner wins. If a user would be both owner and follower, they’re an owner.
  • User details stay in sync. When a user updates their profile, their details on ownership entries update too.

​
Seeds

Ownership travels on the record’s ownership array in a structural Seed — each entry is a user_id and a role: 
"ownership": [
  { "user_id": "695eb58adc6fea533b02a8c2", "role": "owner" },
  { "user_id": "695eb58adc6fea533b02a8c3", "role": "follower" }
]
Templates carry their default_ownership the same way.

​
Governance & permissions

Only a Journey Manager who is an owner of the record — or a super admin / Master — can change its ownership.

​
API access

Dedicated operations add and remove owners and followers on a record, and index endpoints filter automatically by ownership for non-admin users. See the API reference.

Object types

Which object types support Ownership.

Profiles

Set default ownership inherited by new records.