Inloggen en rollen werken meteen. Gebruikers zien alleen de data van hun eigen bedrijf.
Inloggen en rollen werken meteen. Gebruikers zien alleen de data van hun eigen bedrijf.
1
path that decides who a user is
4
roles, compared in one place
0
company IDs accepted from the browser
Zonder een gedeelde basis bouwt elk team deze randgevallen opnieuw — en anders.
One endpoint trusts an ID sent from the browser. One curious user edits it. Now they're reading another company's data, and you're writing the apology email. Here, the browser never gets to pick the tenant. The server does.
Every feature writes its own role check. Over time they disagree. An admin-only action in one screen quietly becomes open to editors in another, and nobody notices until an audit does.
Company-wide members, project-only members, and owners all overlap. Without one rule, every endpoint answers 'who can see this project?' a little differently. That's how weird access bugs are born.
Het mechanisme van begin tot eind, zoals het in de repository is geïmplementeerd.
Clerk checks the login
Clerk confirms the session once per request. No session means the request stops right there.
The login maps to a real user
The server looks the login up in your own users table. An account that isn't set up yet gets a clear error, not a free pass.
Access is checked next to the write
The same database call that saves your data also confirms the user belongs there. There's no gap for a mistake to slip through.
One rule decides roles
Viewer, editor, admin, owner. One comparison function ranks them, and every feature uses it. Company and project access merge with a single rule.
Interactief voorbeeld
Deze rondleiding toont het geïmplementeerde backendcontract zonder account, credentials of providercalls.
Interactief voorbeeld
Alleen deterministische voorbeelddata. De interactie gebruikt geen account-, provider- of netwerkverbinding.
Kernpunten
Every request is checked against a real user in your database. What the browser claims doesn't matter.
Viewer, editor, admin, owner. One ordering, used everywhere, so access never drifts between features.
Missing login, unknown account, or no membership? The request stops with a clear error. Nothing slips through on a lucky default.
Technische garanties
Achter de schermen houden autorisatie, tenantgrenzen en foutafhandeling één duidelijke eigenaar. Zo blijft de snelle ervaring voor gebruikers gekoppeld aan veilig herstel als het misgaat.
De grens hierboven is geen claim maar code. Deze bestanden dragen het contract:
src/server/auth.tssrc/server/permissions.tssrc/policies/roles.tsDeze functies delen contracten en grenzen met deze pagina.
De documentatie beschrijft dezelfde contracten die deze pagina demonstreert.