Skip to content

Identity, companies and authorization

Toolora combines authenticated identity, active company membership, capabilities and resource scope. Browser operations use row-level security. Privileged API operations apply explicit checks before accessing business records or providers. Assignment and portal relationships add resource-specific conditions. The summaries below describe these boundaries; the complete allow/deny matrix remains to be documented.

The frontend uses Supabase Auth for persisted sessions and token refresh. The backend verifies the token and rebuilds current company memberships and capabilities. The browser obtains application permissions from that API identity. Authentication and sessions describes verification, stale-result guards and the limits of the session evidence.

The active company identifies the context for company-scoped work. The API and direct database requests validate the accepted token’s company selection against the same live actor projection. A stored account preference affects future token issuance. The frontend scopes its query cache by company. Active company and membership explains selection, switching and the transition between these contexts.

A capability permits a class of operation in the active company. A privileged handler must separately establish authority over the requested record. Capabilities and resource access traces these checks through project read and completion operations and compares the API and database rules. API policy defines the server boundary.

The customer portal checks live identity and customer authority before returning a customer-safe project projection. Project discovery and detail share a private SQL admission contract; publication and stronger actions retain their own conditions. Contact creation and ROT-recipient selection do not grant new portal access. Customer portal access explains paired company/person identity, independent customer-grant and direct-project-contact bases, safe publication and stronger operation boundaries.

Workers use personal assignments and explicitly released delivery. Subcontractors use company-scoped requests and commitments; submissions remain separate from principal review. Worker and subcontractor access compares these relationships, publication conditions, recovery exceptions and API/database differences. Role surfaces provide navigation without replacing those checks.

The MCP transport verifies a bearer token. Business tools then require a company, live person and ordinary project-read permission, followed by tool/resource checks. Metadata reads have different conditions. MCP authorization documents tool families, continuations, effects and the disabled resource-audience check. The MCP contract owns the interface schema and response conventions.