Mersal Onboarding an associate safely
The situation
A new associate starts on Monday with a caseload to inherit and no reason to see the rest of the firm's work.
What goes wrong without a system
Access is all-or-nothing, so they either cannot work or can see everything, and the boundary is a promise rather than a control.
How it runs in Mersal
Invite with a role
The invitation carries the role, and the seat count is enforced at the point of invitation.
They see their own work
An associate's dashboard is scoped to their matters, tasks and clients rather than the firm's.
New matters route for review
Where the firm requires it, matters they open queue for partner approval instead of going live.
The boundary is enforced at the database
Role scoping is applied in the database, not by hiding buttons, so it holds regardless of the route taken.
Templates carry the house style
Opening a matter from a template means their first file looks like the firm's, without a briefing.
What it prevents
- All-or-nothing access for a new joiner
- A boundary that is only a promise
- Learning the firm's conventions by osmosis
The fastest way to judge this is to watch it run against your own way of working.