01foundation
Identity and session control
Verified accounts, session lifecycle controls, mobile token rotation and explicit organisation context.
Security and governance
Control is part of the product model. Not a badge beside the footer.
VercentLabs is designed around tenant boundaries, explicit permissions, transactional commands and traceable operating evidence.
01
Control foundation
The system should know who can see, change and approve each record.
Security starts with product behaviour and data boundaries before provider certifications or procurement documentation.
02foundation
Role and permission boundaries
Navigation, records and actions respond to the active user permission set rather than visual convention alone.
03foundation
Tenant and branch isolation
Organisation, company and branch scope is enforced in service and database access paths.
04foundation
Audit and decision evidence
Important changes preserve actor, time, context, request and governed decision history.
02
Operational controls
Fail closed. Preserve context. Leave evidence.
The release verifier and database contracts test the controls expected from the current CRM scope.
- Organisation-scoped data access
- Company and branch validation
- Permission-gated navigation and mutations
- Transactional approval execution
- Immutable consent evidence
- Audit-ready record histories
- Signed public CRM capture
- Retryable leased outbox delivery
- Billing entitlement enforcement
Security review
Evaluate the controls against your actual operating risk.
Share your organisation structure, sensitive data, access model, approval boundaries and deployment requirements.