Operate
Day-to-day state across every instance you run — what synced, what is stale, and what needs a person.
OverviewProjects
Operational metadata for REDCap
Operate every REDCap instance from one place.
Access governance, activity analytics, and compliance monitoring for the instances you already run — built entirely on operational metadata, never on study records.
OOperations PlatformSSAdministrator
Operate
Overview
Projects
Govern
Access Requests
Access Reviews
Audit Logs
Analyze
Activity Analytics
Compliance Hub
Settings
REDCap connections
Overview
Export12
Dormant accounts
31
Export / admin rights
4
Inactive projects
2
Unapproved accounts
Access requests
3 pending
Cardiac Rehab Cohortj.okonkwo@example.eduPI
Stroke Registrym.laurent@example.eduViewer
Mobility Outcomesa.silva@example.eduPI
What you can operate
The same four groups you work in.
The console is organized the way the work is. Signing in drops you straight into these — no setup tour, no empty dashboard.
Govern
Decisions about access and the record that proves them, from first request through quarterly attestation.
Access RequestsAccess ReviewsAudit Logs
Analyze
The recurring questions, already answered — who is active, what got exported, what slipped out of policy.
Activity AnalyticsCompliance Hub
Settings
Set up once, revisit rarely — REDCap connections and credentials, admin-only.
REDCap connections
Availability follows your role — access governance is administrator-only.
The data boundary
It never holds a single study record.
The platform reads operational metadata and nothing else. That is not a setting someone can toggle — there is no code path that ingests a record, a response, or a file, so the question of where participant data went never arises.
Stored by the platform
- Projects and instruments
- User accounts, roles, and rights
- Sync and activity timestamps
- Privileged audit events
Never leaves REDCap
- Study records
- Survey responses
- Uploaded files
- Any identifiable participant data
Operating principles
Roles enforced on the server
Administrator, principal investigator, and viewer scopes are applied in the backend — never hidden in the interface.
Every privileged action audited
Actor, timestamp, IP, and user agent are recorded for each change, and the log exports to CSV or PDF on demand.
Syncs you can safely retry
Metadata ingestion is idempotent, so a repeated or resumed run never doubles a record.
Bring your instances into one operational picture.
Accounts are provisioned by your REDCap administration team. Tell us what you need to do and we will get you the right role.