Alleen ons team, alleen ons project, en de server beslist.
Growth-OS bevat onze pipeline, onze gesprekstranscripten, onze besluiten en ons financiële grootboek. Je meldt je één keer aan, en daarna bepaalt de server welke collega je bent en in welk project je zit. Wat de browser beweert, telt niet mee. Je rol bepaalt of je een besluit mag wijzigen of het budget mag openen.
1
path that decides who you are
4
access levels behind every role name
0
project IDs trusted from the browser
Zonder een gedeelde basis bouwt elk team deze randgevallen opnieuw, en anders.
A pipeline spreadsheet cannot tell salary lines apart from a prospect list. Everyone who can open it can read all of it, and nobody can tell you who did. Growth-OS resolves membership per project on every read and every write.
When each screen writes its own check, they slowly disagree. Finance opens to someone who was only meant to read, and nobody notices until an awkward conversation. One ranking function keeps every screen consistent.
Access checked once, when a page loaded, never expires. Here membership is resolved on the request itself, so removing someone from the project actually removes them.
Het mechanisme van begin tot eind, zoals het in de repository is geïmplementeerd.
Clerk confirms the session
Sign-in runs through Clerk once per request. Without a session, nothing after this step runs at all.
The session maps to a teammate
The server looks that login up in our own users table. A login with no teammate record gets a clear error rather than a free pass.
Membership is checked next to the data
The same database call that reads or writes your record confirms you belong to that organization and project. There is no gap between the check and the work.
One function ranks the roles
roleAtLeast ranks viewer, editor, admin and owner, and every WISEPIM role name maps onto one of them. Organization owners keep access to every project; otherwise a project membership wins, falling back to the organization one.
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 matched to a real teammate row in our own database. A session that maps to nobody stops at the door.
Owner, Founder, Admin, Editor, First hire, Advisory, Viewer. They rank into four access levels, compared by one function that every screen uses.
No session, no teammate record, or no membership in the project, and the request stops with a plain error instead of falling through to a default.
Technische garanties
Clerk verzorgt het aanmelden zelf, dus de beschikbaarheid daarvan kunnen wij niet beloven. Wat hier bewezen wordt, is de grens aan de serverkant: welke collega je bent, en wat je daarmee mag aanraken.
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.