Identity proof
A verified identity is required before company matching begins.
CONNECTION STATE
Safely disconnected
The client app is operating in its clearly labeled demonstration mode. No OXS customer records are connected.
IDENTITY BEFORE INFORMATION
One doorway.
Authority never assumed.
The website can become a governed client surface without copying OXS authority. Authentication identifies a person; OXS membership determines exactly which company, tenant, records and actions that person may reach.SERVER-ENFORCED GATES
Every request must pass the full boundary.
Company membership
An email address or domain never grants access by itself.
Tenant authority
Every request is checked against one exact OXS tenant and permission.
Portfolio separation
Portfolio summaries never expand authority inside an operating company.
Record provenance
Synchronized records retain source, version, tenant and timestamp.
Governed writes
Requests return to OXS with actor, tenant, action and idempotency evidence.
ACTIVATION RECORD
What remains before live connection.
- Approved external customer identity provider and recovery policy
- Verified OXS customer API endpoint, audience and server credential
- Identity-to-company and identity-to-tenant membership verification
- Role and permission acceptance tests, including cross-tenant denial tests
- Read and write audit-event verification with an authorized test tenant
- AJ approval before enabling production customer records