Enterprise communication needs visible devices, clear roles and revocable access — not just a user list.
WebAuthn routes, device/session endpoints and management interfaces.
No tenant model, SSO or SCIM provisioning.
Release script, claim verification, schema-to-migration alignment, browser walkthroughs and a server-side rehearsal of pending migrations in a disposable clone of the running data.
An internal release gate is not a penetration test or operating certification. The migration rehearsal does not modify the running data; an actual recovery exercise from the encrypted backup remains a separate operational proof.
Product, security, status and release documentation use the same controlled-release status.
No general availability, certification or approval for highly regulated use.
The admin dashboard exposes accounts, roles, email-verification state, suspension, devices, active sessions and login history. Administrators can suspend access and revoke sessions globally.
An account is more than an email address. Connect treats devices as security objects linked to sessions, keys and verification state.
Shared Zod contracts and versioned endpoints align web, realtime and future integrations. Business logic remains inside modules rather than page components.
Organisations, SSO, SCIM, policies and audit exports are not pretended to exist. The architecture prepares them, but each needs its own model and acceptance work.
Keep ultimate administrative responsibility visible.
Manage accounts, roles, devices and sessions.
Disable access immediately and visibly.
Review login events with limited retention.
Issue single-use hashed invitation codes.
Verified email and token-bound password recovery; account deletion remains a separate confirmed security operation.
“Security scales only when responsibility scales with it.”
VENTEX enterprise principle
The current administration model works today; tenant features follow separately.
