Skip to content
All stories
LogisticsRBAC

Meridian Freight modelled roles once and stopped arguing about them

Permissions had been a boolean column. Then a customer asked for read-only auditors.

Illustrative example

Meridian Freight is a composite example, not a named customer. The situation and the way it was solved are drawn from what teams actually bring to us; the company itself is invented. Real customer stories are published only with the customer’s permission and their own name on them.

3
roles replaced 14 boolean flags
per-tenant
role assignment
<1ms
permission check

The situation

Access control had grown one flag at a time. Nobody could answer what a given user could actually do without reading the code.

What they did

Roles are defined once per project and assigned per organization membership, so the same person can be an admin in one tenant and a viewer in another.

What changed

Permission checks moved into the request path with a slug rather than a role name, so renaming a role no longer breaks anything.

Add SSO, the easy way

Everything in this story is something the platform already does. Start with the quickstart and have a working sign-in this afternoon.

What’s your enterprise story?

Tell us what the checklist is costing your team and we will give you a straight answer on fit.