All guides

Admin Guide

Users, roles, and workspaces

Settings → Users; Settings → Members / Workspaces tabs

Company administrators invite users and manage membership; workspace permissions control read, run, approve, and manage operations. The last active company administrator cannot be removed or demoted.

Platform rights do not create company membership. Platform administrators see company metadata, not agents, prompts, workflow content, run input/output, approval content, private files, connector settings, or secrets.

Model providers, budgets, and usage

Model Providers → Providers / Budgets / Usage

Configure the supported server-resolved OpenAI and Anthropic built-in aliases and workspace budgets. Actual token reports and estimates are distinguished; unknown outcomes retain conservative reservations.

Bring-your-own-key transport, private models, model tool calling, and streaming are not yet available. Never paste model keys into a free-text field.

License activation and limits

Settings → Licence; /license/activate for a new licensed company

Activate a VX-AOS key issued by VisionX License Manager. New-company activation requires verified email and MFA. Signed license features and quantities are authoritative; company users cannot edit them.

Starter, Professional, and Enterprise are the sold editions. Real monthly runs are counted per company per UTC month. Concurrency is per company. Administrators are warned at 80% and 100% of the monthly run allowance. Reserved capabilities are not yet available, not an upgrade promise.

Read-only mode

Settings → Licence; company status notice

An expired license or ended trial blocks new runs, creations, and invitations. Data remains available and administrators retain authorized export access. Started runs are not stopped by expiration or quotas.

Suspension shows “Company suspended, contact VisionX.” New schedules and webhooks are blocked while existing started work keeps its completion path. The platform console cannot lift a signed suspended or revoked license.

Audit retention and legal holds

Settings → Backup & retention

Owners can preview eligible audit entries and the oldest date kept. Retention uses the unified license policy with a minimum of 90 days and a durable 30-day first-removal warning.

A legal hold with a reason prevents deletion. The sole retention function records permanent batch counts, date ranges, policy, and SHA-256 evidence before removing eligible entries. Manual “run retention now” uses the same checks. Automatic daily execution remains unverified.

Configuration and record backups

Settings → Backup & retention

A verified company owner with MFA and a reason can request, verify, and download an exact configuration-and-record snapshot. Durable stage progress, fenced 120-second worker leases, and failure cleanup protect recovery and owner-only access.

Current limits: 5,000 rows, 8 MiB snapshot, 1 MiB per kind, 16 MiB final JSON, and 40 nesting levels. Capture and assembly are whole capped operations, not size-independent row batching. Above a limit the job fails; it never produces a truncated download.

New packages expire seven days after completion; the owner sees the expiration time. Uploaded files, dry run, and restore are not yet available. Structured secrets are excluded, but secrets pasted into free-text fields cannot reliably be detected and may be included as written.

Audit and exports

Settings → Backup & retention → audit export; Settings → Plan & Licence → Export company records; Runs → CSV; Platform → Audit log

Database-triggered audit records and decision/event history are append-only. Authorized exports are scoped to the selected company. Platform actions use a separate metadata-only audit with reasons and before/after values.

Retention-batch checksums and immutable approval evidence do not constitute a cryptographic chain of the entire live audit log. No certification or tamper-proof claim is made. General company data erasure and full atomic restore are not available.

Integrations settings

Limited

Settings → Integrations; Tools & Connections

Use connection definitions, detail, testing, and revocation. Domain-name outbound REST execution is disabled. Only approved exact public IP-literal HTTPS requests can execute.

Named Microsoft, Google, ERP, CRM, messaging, database, and MCP integrations are Planned. Do not treat a definition or sandbox example as a working live integration.

Website trial flow

/trial/activate or /trial/redeem; Platform → Website trial activation

The platform owner controls website trial activation, off by default. Both public pages accept a website activation key. A trial key is separate from a VX-AOS license key.

When enabled, the server verifies the website signature and redemption response. Sign in or sign up with the exact email on the key, verify email, and complete MFA. A successful redemption creates a new company only; it never replaces an existing company’s entitlement.

The website plan determines Starter, Professional, or Enterprise limits. Trials last the signed number of days (14 when omitted), then become read-only until an AOS license is activated. A retry of the same key resumes the same request; an unknown redemption outcome is not blindly retried.