Team features are usually described as a permissions matrix. The part that actually matters is underneath: whether one workspace can reach another’s data, and whether you could prove it either way. This page is about both.
| OwnerThe workspace belongs to them | Everything |
|---|---|
| AdminRuns the workspace day to day | Nearly everything |
| MemberDoes the work | The work |
Three, not fifteen. A permissions model nobody can hold in their head gets set once and never reviewed, which is worse than a simple one people understand.
You invite by email address. The invite is a record with its own lifecycle rather than a shared link — so an invite that was never accepted is visible, and one that was is attributable.
WhatsApp conversations carry an assignee and a status, which is what stops two people answering the same business with different answers. Unassigned is a real state — it is the queue — and there are settings for how conversations get distributed.
The shared inbox in full: statuses, labels, assignment and private notes.
Every row of customer data belongs to a workspace, and the boundary is enforced at the database level rather than by application code remembering to add a filter to each query.
A filter that has to be written into every query is a filter that will eventually be missed in one — and the one it is missed in will be a new feature written under time pressure. Enforcing it underneath means the failure mode is a query that returns nothing, rather than a query that returns somebody else’s customers.
Data access is logged. This exists because India’s DPDP Act expects it, but it is also what turns the isolation claim above from an assurance into something checkable after the fact.
What Rechlio does with personal data, how long it is kept and how to have it deleted are in the privacy policy, the DPDP compliance page and the data deletion page.