Access in Merdial is a per-page grant list, not a fixed role. A member’s effective access is what the organisation has enabled, intersected with what that person has been granted. Roles are presets that seed the list.
The hierarchy
Owner account
└─ Organization the tenant root
└─ Department(s) the real isolation boundary
└─ Accounts / campaigns
└─ Agents, leads, calls, appointmentsThe department is where isolation actually happens. Every record carries both an organisation and a department, and the database enforces the pair — so an agency running five client teams inside one account gets five isolated data sets, with no cross-department leakage.
The presets
| Role | Scope |
|---|---|
| Owner | Everything in the organisation: every page, billing, ghost mode. |
| Manager | Ops dashboard, live floor, review queue, coaching, the account brain. |
| Agent | Their own calls, leads and appointments; the leaderboard; attendance. |
| Client | Read-only. Approved leads and appointments for their own campaigns, nothing else. |
Ghost mode
An owner can view the product exactly as a member sees it — useful for “it looks wrong on my screen” and for checking what a client can actually see before you invite them. It is display-only: an action taken while ghosting is never attributed to the person being ghosted.