Demo Accounts

Demo Personas — Tour as Different Roles

Five example personas show what each kind of user can do, what they cannot do, and where they land on login. Pick one to tour the platform from that perspective.

Personas

Permissions

Distinct landings

Autonomy classes

A0–A3

Avery Platform-Admin
Platform Adminavery.admin@example-cro.com
Owns the AI-Native CRO platform. Configures agents, model registry, policy, and tenant access. Reviews the full operational picture every morning.
Autonomy access
A0A1A2A3
Can do
- Configure agents, prompts, and the model registry
- View every study, signature, and provenance trail
- Manage users, roles, and tenant settings
- Approve and promote staging records on any study
- Adjust risk thresholds and policy guardrails
Cannot do
- Bypass the Part 11 e-signature gate (no one can)
- Make the causality call on a safety report (A4 is prohibited)
- Delete provenance or audit trail rows
Landing page
/digest
Tour as this persona
Sam Sponsor-User
Sponsor Usersam.sponsor@acme-pharma.com
Sponsor representative for an ongoing oncology study. Files requests, reviews signed artifacts, and watches study progress through the sponsor portal.
Autonomy access
A0A1
Can do
- View their own studies and dashboards
- File and track sponsor requests
- Download signed artifacts and evidence bundles
- Comment on staged outputs scoped to their studies
Cannot do
- See other sponsors’ studies or data
- Promote staging records to live
- Change agent configuration or model selection
- View internal QA findings outside their scope
Landing page
/portal
Tour as this persona
Olivia Ops-Lead
Clinical Operations Leadolivia.ops@example-cro.com
Clinical operations lead for multiple active studies. Triages the staging queue, watches risks, and decides what gets promoted to live each day.
Autonomy access
A0A1A2
Can do
- Triage the staging review queue
- Approve or reject agent-staged outputs
- Review the risk register and mitigations
- Trigger reruns of agents within policy limits
- See the full activity timeline across studies
Cannot do
- Sign on a sponsor’s behalf
- Edit the model registry or prompt versions
- Promote without a valid Part 11 signature
Landing page
/digest
Tour as this persona
Quinn QA-Lead
QA Leadquinn.qa@example-cro.com
Owns quality and validation. Audits agent outputs, tracks CSV/CSA evidence, and signs off that the platform stays inspection-ready.
Autonomy access
A0A1A2
Can do
- View Part 11 + ALCOA+ compliance dashboards
- Browse and download CSV/CSA validation evidence
- File quality findings on staged outputs
- Audit signatures and the provenance graph
- Sign off on validation packages
Cannot do
- Make causality calls or safety determinations
- Edit agent prompts or model assignments
- Promote records without a counter-signature
Landing page
/compliance
Tour as this persona
Ingrid Inspector
FDA Inspectoringrid.inspector@fda.example.gov
FDA inspector with read-only access for a focused inspection. Pulls evidence binders, traces a signature back to the action that produced it, and verifies provenance.
Autonomy access
A0
Can do
- Read the inspection package and evidence binder
- Trace any signature to its full provenance trail
- Export evidence bundles for the audit record
- View signed artifacts and Part 11 metadata
Cannot do
- Write, edit, or comment on any record
- See unsigned drafts or staging working copy
- Trigger agents or promote records
- Access sponsor data outside the inspection scope
Landing page
/inspection
Tour as this persona

Personas

Avery Platform-Admin

Sam Sponsor-User

Olivia Ops-Lead

Quinn QA-Lead

Ingrid Inspector