01
Organisation-scoped records
Operational queries and mutations are scoped to the signed-in organisation. Related assets and assignees are checked before records are created or changed.
Security · Platform controls
Scoped · Auditable · Reviewable
Operational access.
Clearly controlled.
BeltLabs keeps customer workspaces separate, limits access by role and preserves a record of important activity. Deployment-specific commitments are documented during purchasing.
02
Role-based access
Workspace roles separate owner, administrator and member access. Administrative and customer-facing areas use distinct authentication paths.
03
Protected sessions
Session cookies are HTTP-only and use secure production settings. Redirect destinations are restricted to valid internal application routes.
04
Audit and accountability
The platform records important operational and administrative events so teams can trace changes back to a user, action and time.
05
Controlled files and sharing
Stored-file requests validate metadata and ownership. Shared customer records use scoped links rather than exposing the internal workspace.
06
Deployment review
Hosting region, retention, recovery, integrations and enterprise security requirements are confirmed for the deployment being purchased.
Procurement and disclosure
Review the controls against your operating requirements.
Security controls reduce risk but cannot guarantee absolute security. Deployment-specific certifications, service levels, data residency and recovery commitments apply only when expressly recorded in an executed order or schedule. Send security questions and responsible vulnerability reports to support@beltaxis.com.