Admin guide
Users and roles
Platform administrators use User management to invite or create users, choose their workspace and role, review last sign-in, deactivate/reactivate accounts, reset passwords and reset an authenticator.
Never deactivate, delete or demote yourself. At least one active administrator must remain. Temporary-password users must change their password. Email changes require verification.
Security and sessions
Settings → Security provides the idle timeout, network allow-list, audit viewer and retention controls. Authenticator verification is mandatory for every user. External sign-in is off unless a platform administrator enables it for the company.
Before sensitive account changes, verify a fresh authenticator code. Account recovery codes are prepared behind a held database change. A code only resets an authenticator after password sign-in; a new authenticator must then be enrolled and verified.
Audit and retention
Audit records are hash-chained and append-only. Filter by actor, action and date; exports are audited. Secrets are masked. The configured default audit retention is 365 days, with supported values from 90 to 2555 days.
Automatic audit purge stays off pending owner approval. Setting a retention value is not evidence that a purge ran. Legal holds and evidence retention must be considered separately.
Trial administration
Only a platform administrator with MFA may open trials, extend an expiry or convert a trial. The opening switch defaults closed and is prepared in a held change; no trial opening is performed by this guide.
VisionX Starter maps to Starter; Growth maps to the existing Professional tier; Professional and Enterprise map to their matching tiers. Unknown plans are refused. Confirm the Growth mapping with the product owner before rollout.
Limits and integrations
Review upload size, monthly analysis quota, live-call cadence, monitoring caps and account-wide provider budgets before enabling a workflow. Trial expiry guards are prepared for detector calls, external intelligence/search, meeting bots, monitoring and uploads.
No payment or public publishing flow is present. No new third-party account or purchase is required by the prepared changes. Existing paid detector/search services may need funded accounts; never use test calls to verify balances without authorization.