What Sidecar does with the workflow you rely on.
Sidecar is built to become a daily operating record for customer-required document work. This page explains the current safeguards and boundaries plainly, without borrowing an enterprise security costume three sizes too large.
Workspace separation
Authenticated workspace records are separated by tenant in the application. Sidecar is designed so one customer workspace does not become visible inside another customer workspace.
Public demo isolation
The public demo uses separate demo data and safe simulations. Demo request sends do not deliver real outbound email, and simulated inbound messages do not expose or modify an authenticated customer workspace.
Review before workflow changes
Inbound email and OCR-assisted intake are review-first. Sidecar can bring replies, attachments, and suggestions into the relevant workflow, but users confirm what should be linked, updated, cleared, or created. Sidecar does not treat a reply or extracted date as an automatic compliance decision.
Current state and history
Current workflow records control visible status, waiting state, and follow-up dates. Activity and request history provide evidence of what happened without silently overriding the current record. That distinction helps prevent an old email or audit row from bossing around today’s workflow.
Imports and re-imports
Spreadsheet imports are analyzed and reviewed before approval. Sidecar preserves unsupported context where possible and treats later re-imports as proposed changes rather than permission to overwrite records already maintained in Sidecar. Import quality still depends on the source workbook, which is why complex cleanup is scoped separately.
Exports and portability
Workspace data can be exported to XLSX or CSV for reporting, review, backup, or migration. Sidecar should remain useful because it improves the workflow, not because leaving is artificially painful.
Backups and recovery
Sidecar maintains operational database backup and restore tooling with verification and a documented recovery path. Workspace exports support customer portability, but they are not treated as a substitute for operational database recovery.
Email routing
Authenticated workspaces can use configured inbound email routing so replies return to Sidecar for review. The public demo simulates this workflow instead of inviting visitors to send real messages or store real attachments in a shared demo environment.
Product boundaries
Sidecar organizes tracked requirements, documents, requests, waiting states, tasks, expirations, and supporting history. It does not provide legal or insurance advice, verify coverage, certify compliance, approve contractors, predict portal acceptance, or replace customer-required portals.
Current maturity
Sidecar is in early access. That means the core workflow is available, but customer proof, onboarding patterns, and operational documentation are still being strengthened with early adopters. Questions about a specific security, retention, or implementation requirement should be addressed before a pilot begins.