TRUST & SECURITY

Your organisation stays your organisation.

OrgSpace is designed so access follows authenticated identity, organisation membership and job responsibility. Sensitive decisions are checked by the backend, not trusted to whatever a phone or browser happens to display.

Security overview · updated 15 August 2026

IDENTITYAuthenticated accessPeople sign in with their own account. Organisation membership determines which organisation they may enter.

PERMISSIONSRole-based boundariesStaff, managers, administrators, approvers and finance users do not all receive the same access.

ACCOUNTABILITYImportant actions leave historyApproval, platform and payment-scheduling workflows retain who acted and when.

Organisation isolation

Organisation records carry their organisation identity and access is checked against the signed-in person's active membership. Being an administrator in one customer organisation does not grant access to another.

Server-side decisions

High-impact workflows such as joining an organisation, entitlement changes, plan capacity and approval routing are enforced by backend functions or security rules. Hiding a button is not treated as a security boundary.

Sensitive records

Signatures, requisition attachments, private membership details and protected fleet files use separate storage or document paths with tighter role or workflow-based access controls than ordinary operational information.

Approved financial records

Requisition approvals retain the approver and time. Final approved records and their supporting-document relationships are protected so an old approval cannot quietly become a different document later.

Organisation lock state

Billing lockout is designed to stop new operational work without deleting the organisation's history. Authorised administrators retain the ability to read and export records needed to resolve the account or leave the service.

Payment separation

OrgSpace does not need to store full bank-card details. Card checkout is designed to take place on the payment provider's hosted flow, while OrgSpace stores the organisation's subscription and payment references needed for entitlement and audit history.

Device & offline behaviour

Optional biometric unlock uses the device operating system's biometric facility; OrgSpace does not receive the biometric template. Offline storage is limited to supported app work and sensitive datasets are not treated as ordinary long-term cache.

Platform administration

OrgSpace's own App Admin access is separate from customer organisation roles. Platform administrators are explicitly listed in a protected platform-admin record and platform entitlement changes are audited.

Account deletion, privacy and exports

Users and organisations have documented privacy and account-deletion routes. Where organisation records need to be retained for legitimate operational history, the deletion process distinguishes a person's login account from the organisation records the organisation owns. Authorised portals provide exports for supported records.

Security concern?

Use the Support page or contact Pixels. Do not send passwords, complete bank-card details or unnecessary identity-document images in a support message.