Documentation
Operational architecture
A technical description of the platform’s operating model without exposing deployment internals.
Need a hands-on starting point?
Run a free assessment or talk to the team if you want help evaluating fit, permissions, or rollout approach.
Core platform components
TenantVigil operates as a multi-tenant application with separate customer and admin experiences. The customer portal focuses on posture, control evidence, remediation, and reporting. The admin portal focuses on tenant operations, issues, and operational oversight.
The platform stores tenant-scoped assessment results, evidence, resolution state, scheduling configuration, and audit history so technical users can review both the current condition and the operational timeline of a tenant.
Telemetry and operational feedback
Portal, onboarding, auth, report, and control-refresh failures are captured into tenant-aware telemetry and surfaced to administrators through the admin issue views. This allows support and engineering teams to reason about customer-affecting failures without relying on screenshots alone.
What is intentionally not documented here
This documentation describes the product’s permission model, operating flows, and supported functional areas. It intentionally avoids disclosing source code, infrastructure secrets, or deployment-specific internals that are not required for customer understanding or security review.