What this role is, and who it is for
You run the study. You staff it, you open its sites, you move it through its states, you take its versions through UAT to Live, and you are the author leg of the three-way release sign-off. You are named when the study is created, by the Organization Admin, so a study never exists without someone to run it (Create a study). Nobody has to give you a breakpoint to staff the team: you add any study or site role, and only a role that would give you more than you hold yourself is compared (Who can and cannot).
Where you work
| Where | Screens |
|---|---|
| Organization | Studies, Form Library, Settings, Library form builder |
| The study (outside UAT and Live) | Overview, Study Versions, Documents, Exports, Audit Trail, Study Team, Study Settings |
| Build | Build (dashboard), Corrections, Amendment, Saves, Forms, Visit Schedule, Visit and Form Mapping, AI Workstation, Form builder |
| UAT and Live | Dashboard, Forms (the design this workspace runs, read-only), Visit Schedule (read-only), Mapping (read-only), Sites, Participants, Casebook, Queries, AE Log, SAE Log, SDV Plan, SDV Monitoring, Exports, Reports: Enrollment, Reports: Site performance, Reports: Query aging, Reports: Visit compliance, Reports: Protocol deviations, E-Signatures, Audit Trail, Site: Queries, Site: Documents, Site: Staff, Participant: Queries, Participant: AEs and medications |
| UAT only | Issues, Results |
| Live only | Site Team, Reports: Lock readiness |
What you can do
Design and versions
- Build forms, the visit schedule, the mapping and the rules alongside the designer, and use the AI form generator (Build a study, Design forms).
- Submit a version to UAT, close a UAT cycle as passed or failed, raise and read UAT issues, take a passed and approved version Live by typing its version number, withdraw a version and start an amendment (Test a version in UAT, Sign off a version and go live, Amend a live study).
- Apply the author sign-off with a fresh code. The capacity comes from your role; you cannot choose it, and you cannot also sign as QA or approver.
People and sites
- Staff the study team from the organization and add sponsor staff; mark protocol training complete; suspend or retire assignments (Staff a study team).
- Register sites, activate them through the ethics gate, suspend, reinstate and close them, provision site staff and propose their delegations (Open a site, Staff a site). The principal investigator, not you, signs a delegation.
The study's state
- Put the study on hold, resume it, close it to enrollment, complete it, and request a database lock or unlock with an e-signature; a different person confirms (Change the state of a study, Close and lock a study).
Quality and oversight
- Raise queries; report adverse events and deviations and move deviations through review; reconcile a serious adverse event with the safety database; define the SDV plan (Work with queries, Report a deviation, Review and reconcile a serious adverse event, Monitor and verify data).
- Run and download exports; upload, version, approve and archive study documents; read the audit trail, the reports and the dashboard (Export data, Manage documents, Use the reports and the dashboard).
Every permission this role holds
42 permissions (template version 7).
| Permission | What it allows | Held at | Risk | Constraint |
|---|---|---|---|---|
user.directory.read | Browse the organization user directory (for team staffing) | organization, study | standard | |
ai.generate | Generate or edit forms with AI | organization, study | standard | |
audit.read | Access audit trail | organization, study, site | standard | |
document.read | View, download, and preview study documents | organization, study, site | standard | |
document.write | Upload documents, add versions, edit metadata | organization, study | standard | |
document.manage | Approve and archive study documents | organization, study | standard | |
export.read | View export history | organization, study | standard | |
export.run | Trigger ad-hoc and signed exports | organization, study | critical | |
form.read | Open forms and view answers | organization, study, site | standard | |
form.design | Edit form templates in builder | organization, study | standard | |
form.publish | Publish form versions to live | organization, study | standard | |
form.freeze | Marks a role as data-locking authority (separation of duties: cannot also enter data) | organization, study | standard | separation of duties (enter-vs-lock) |
sdv.configure | Define the SDV / risk-based targeting plan (which fields require source verification) | organization, study | standard | |
clinical.query.read | View queries | organization, study, site | standard | |
clinical.query.raise | Open a new manual query | organization, study | standard | separation of duties (query-raise-vs-answer) |
clinical.event.read | Read a subject’s events and the adverse event and SAE logs | organization, study, site | standard | |
clinical.event.report | Set the safety report status of a serious adverse event and its awareness time | organization, study, site | standard | |
clinical.event.reconcile | Record the reconciliation of a serious adverse event with the safety database | organization, study | standard | |
deviation.report | Report and update protocol deviation status | organization, study, site | standard | |
site.read | View site details | organization, study, site | standard | |
site.write | Create / edit sites and staff | organization, study | standard | |
site.activate | Activate a registered site | organization, study | elevated | |
site.transition | Transition site lifecycle (suspend / resume / close) | organization, study | elevated | |
study.read | View study details and dashboards | organization, study, site | standard | |
study.write | Edit study settings and teams | organization, study | standard | |
study.state.change | Hold, resume, close to enrollment and complete a study | organization, study | elevated | separation of duties (enter-vs-lock) |
study.lock | Lock and unlock the study database (two different people, each with an e-signature) | organization, study | critical | needs an e-signature; separation of duties (enter-vs-lock) |
subject.read | View subject data | organization, study, site | standard | |
team.assign | Assign / provision a study team role | organization, study | elevated | |
team.manage | Suspend / resume / retire team assignments | organization, study | elevated | |
team.training_complete | Mark a team member as protocol-training complete | organization, study | standard | |
study.version.read | View the study's versions: the version list, UAT cycles, sign-offs and the changes between versions | organization, study | standard | |
study.amendment.start | Start an amendment (the next version of a Live study) | organization, study | elevated | |
study.version.submit_uat | Submit a version in Build to UAT (freezes its design and opens a UAT cycle) | organization, study | elevated | |
study.uat.close_cycle | Pass or fail the open UAT cycle (a failed cycle returns the version to Build) | organization, study | elevated | |
study.uat_issue.read | View the issues and results of a UAT cycle (what testers found, and what became of it) | organization, study, site | standard | |
study.uat_issue.write | Raise, edit, resolve, accept and reopen the issues of the open UAT cycle | organization, study, site | standard | |
study.version.signoff | Sign off a version that passed UAT (author, QA or approver; three different people) | organization, study | critical | needs an e-signature |
study.version.go_live | Take an approved version Live (supersedes the version that was Live) | organization, study | critical | |
study.version.withdraw | Withdraw a version that has not gone Live | organization, study | elevated | |
visit.read | View visit schedule and data | organization, study, site | standard | |
workflow.design | Build and edit workflows | organization, study | elevated |
What you cannot do, and why
- Create a study or archive one. Creating and archiving are the Organization Admin's.
- Enter or correct clinical data. You can read every form, not write a value.
- Answer, close or reopen queries. You raise them; the site answers and an independent reviewer closes.
- Verify data against source. That is the monitor's job, and the person who entered a value never verifies it.
- Apply an investigator signature or sign a delegation. Only the principal investigator can: nobody signs their own entry.
- Confirm a lock or an unlock you requested. Two different people lock and unlock the database.
- Sign as QA or approver. Three different people sign a version.
- Add an Organization Admin to the team, give anyone a second role on the study, or add an organization member to a site team. The rules are on Who can and cannot.
What the system records
study.version.* (submitted, signed off, went live, withdrawn), study.amendment.started, study.state.changed, study.lock.initiated, team.role_assigned, team.assignment_changed, team.delegation_proposed, site.registered, site.activated, site.transitioned, sdv.plan_updated, query.raised, deviation.status_changed, event.reconciliation_recorded, export.*, document.*. See Audit events.
Seen in the simulation
Could: staff the study team from the organization; register and activate sites (in UAT and in Live), provision site staff and propose delegations; submit to UAT, pass or fail UAT cycles, sign as author, take a version Live; start an amendment; set the SDV plan; move deviations through review; put the study on hold, close it to enrollment, complete it; request a lock and an unlock and withdraw a request. Could not: sign a delegation; confirm a lock or unlock the same person requested; archive; add an Organization Admin, add a second role to the same person, or add an organization member as external staff. Roles other than the build team's (Clinical Research Associate, Medical Officer and so on) were accepted on a study in Setup.
Compliance Q&A
Yes. The Project Manager signs as author, the Data Manager as QA and the Sponsor Manager as approver, each with a fresh code, each bound to the design the passed UAT cycle tested. The designer and the Organization Admin have no control to sign.
Evidence: server versions sign-off (capacity derived from rolethree different peoplebound to the tested snapshot)simulation of 20 Oct 2026, steps 5 and 6 (author, QA and approver signatures with step-up codes)
No. The Project Manager holds no permission to write a value, answer or close a query, verify against source or sign as investigator. The study team reads and queries; the site writes.
Evidence: role-catalog project_manager (no form.write, no sdv.perform, no clinical.query.answer or close)simulation of 20 Oct 2026
Related
Create a study · Staff a study team · Review and release a study · Open a site · Close and lock a study · Who can and cannot