Skip to content

Portal surfaces and audiences

Toolora’s portals present different parts of shared business work. Customer project collaboration, principal worker execution, subcontractor commitments and public quote responses have distinct admission rules. Reusing a layout or a file viewer does not merge their audiences or permissions.

Portal routes use a reduced shell rather than the office navigation. Their backend policies still establish the exact actor and resource. Actor contexts defines the participating identities; this article explains the surface each sees.

Surface Entry and task Admission and visibility
Customer /customer, paired customer/company links and /customer/projects/:pkProject Exact live person/company admission; customer-wide grant, historical self relation or direct-project contact; safe published projection
Principal worker /worker and assigned-project routes Live principal worker context, assignment/publication and own-work operation rules
Field stream /falt Principal staff or worker surface; subcontractor company excluded
Subcontractor (UE) /ue, including commitment deep links Own UE identity plus request/award/commitment scope in the principal’s work
Public quote /quote/public/:shareToken Quote-token and offered-version lifecycle; independent of authenticated customer project admission

The frontend worker guard requires a worker flag and excludes subcontractor tenant classification. Principal staff and workers share some field functions, but a staff flag alone does not satisfy every worker-route guard. UE staff remain in the UE workspace. Actual read/write permission belongs to the endpoint and resource policy.

Customer lists and project detail use the same SQL admission owner. A customer is selected as a customer-party/company pair; customerPortalCustomerPath preserves both. The frontend must not infer the company from response order or the internal office workspace.

Direct project contact is an independent project-only basis. It does not grant access to every project of that customer or allow customer-wide recipient edits. The API obtains the admitted person/project context, then applies stronger operation-specific conditions. Transactional completion and protected dossier actions retain their own rules. See customer portal access.

Admission and publication are separate. A person can be admitted to a project while internal notes, procurement details, files or work orders remain hidden. Customer-safe projections intentionally avoid returning raw internal project rows under browser RLS.

Workers see published assigned work and act within their execution context. Time reporting, photos and completion/review have their own ordering and authority. An office approval is not implied by a worker submission.

UE requests, responses and awards lead to commitments and submissions. That path must not expose the principal’s customer finances or internal procurement to another audience. Existing UE conversation, closure and photo-ordering limits remain documented in subcontractor workflow and assignment policy.

Conversation participants, message visibility and attachment retrieval add separate audience checks. A resource link or participant seat does not make every message visible. Conversation audiences and Storage own the detailed retrieval rules.

A synthetic customer contact opens one directly assigned project in Company B while signed into an office workspace in A. The project API admits the exact B/person context. The contact can see published project material but is refused a customer-wide recipient edit without that stronger basis. Changing the URL to another project must cause a new admission check.

The source review establishes the route, projection and helper contracts. Deterministic denial tests do not alone verify real token issuance, all devices or a full working day. Source-level completion of this topic does not close the independently tracked business scenarios.