Access Requests
Pending
0
Approved
0
| Date | Organization | Status | Actions | |
|---|---|---|---|---|
| Loading... | ||||
Users & Tenant Access
| User | Login | Tenant Access | Account Status | Projects | Created | Actions |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Tenant Rescue
Audited support access
Select the tenant from the catalog, confirm the UUID and tenant key, then grant temporary admin membership for the support case. This is not user impersonation or a password bypass.
Select or searchUse the tenant catalog dropdown, or search by tenant UUID, tenant key, name, or owner email.
| Tenant | Support Admin | Status | Expires | Reason | Created |
|---|---|---|---|---|---|
| Loading... | |||||
System Documentation
Loading the generated documentation catalog...
System Admin Users
| Tier | Status | Protected | Created | Actions | |
|---|---|---|---|---|---|
| Loading... | |||||
System Messages
Loading...
System Health & Security
Supabase
Checking
Cloudflare
Checking
Malware Scanner
Checking
Storage Coverage
Checking
Security Signals
0
File Findings
0
MVP startup capacity
Live, PHI-safe request and database signals for the current Micro tier. HEALTHY, WATCH, WARNING, and CRITICAL use sustained configurable thresholds; a missing telemetry signal is visible and never treated as healthy.
API p95 · 15 min
Checking
API errors
Checking
Database CPU
Checking
DB connections
Checking
Active sessions · 15 min
Checking
Heavy work active
Checking
Loading telemetry coverage.
| Signal | Current | Threshold / Reserve | Status |
|---|---|---|---|
| Loading... | |||
Tenant workload fairness
Imports, exports, integrations, and rule batches use bounded tenant and global leases. Limits protect ordinary clinical work; expired leases recover automatically.
| Workload | Active | Throttled · 15 min | Failed · 15 min | Tenant / Global Limit |
|---|---|---|---|---|
| Loading... | ||||
| Top tenant · 15 min | Requests | Average latency | Errors |
|---|---|---|---|
| Loading... | |||
Micro upgrade triggers
Upgrade only after a sustained trigger, not a single short spike. Fix queries and workload behavior before resizing when software is the cause.
Loading configured triggers.
Platform dependencies
Local application probes are shown separately from vendor-wide status pages so a global green status cannot hide a CRP Studio outage.
| Service | CRP Studio Check | Vendor Status | Details |
|---|---|---|---|
| Loading... | |||
Scheduled perimeter monitoring
Checking scheduled protection for System Admin and the main SaaS.
| Application check | Status | Finding |
|---|---|---|
| Loading perimeter results… | ||
Only critical service or security issues are emailed to the selected administrator’s verified email of record. Lower-priority findings remain in this dashboard.
Potential security threats
Aggregate, PHI-safe indicators from file quarantine, server-side rate limiting, and Cloudflare security analytics. A signal requests investigation; it is not proof of compromise.
| Severity | Signal | Count | Window | Recommended Action |
|---|---|---|---|---|
| Loading... | ||||
Service and schedule
Checking ClamAV, object coverage, and background schedule.
Last status check
Not checked
Last clean scan
No evidence loaded
Background schedule
Checking
Last 24 hours
No evidence loaded
File findings and remediation
Automatic retries recover transient scanner failures. Use Retry now after correcting a service problem. Purge permanently deletes only a definitively blocked quarantine copy and requires a reason.
| System Area | State | Finding | Attempts | Last Checked | Next Action | Remediation |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Audit Logs
Patient audit trails are available in Operations.
Loading...
| Time | Actor | Action | Resource | Details |
|---|---|---|---|---|
| Loading... | ||||
Disaster Recovery
Overall Readiness
Setup Required
Maximum Data Loss
15 minutes
Recovery Target
Same business day
Upload Scanner
Checking
Restore Rehearsal
Not Tested
Upload security service
Supabase keeps the quarantine, background queue, and audit trail. AWS Lambda runs ClamAV for new uploads and scheduled whole-system storage re-scans.
Checking scanner health. Uploads fail closed while health is unknown.
Last health check
Not checked
Uploads in the last 24 hours
No evidence loaded
An outage never bypasses scanning: files remain quarantined and unavailable until the scanner recovers. No token, file name, tenant, participant, or file content is displayed here.
Your two decisions
The recommended defaults are selected. Change them only when a study or customer requires different recovery targets.
Preparation checklist
These checks remember planning progress on this device only. They never change the official “Not Tested” status.
Important: checking every box means the rehearsal is ready to run—not that disaster recovery has passed.
1. You approve
Confirm the recovery targets above and authorize any provider cost. You do not run technical commands.
2. Helper configures
The helper verifies database backups and configures separate recovery for uploaded files.
3. Helper rehearses
The helper restores to a separate environment and tests access, audit, signatures, exports, randomization, and files with synthetic data.
4. You approve
Review the evidence and sign the result. Only a passed rehearsal changes disaster recovery from “Not Tested.”
Technical helper handoff
These protected commands are for the recovery helper. Tokens are never entered into this browser.