Skip to content
ImplementedFor study and project managers at sponsors and research organizations

Project Manager

Last updated Oct 21, 2026

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

WhereScreens
OrganizationStudies, Form Library, Settings, Library form builder
The study (outside UAT and Live)Overview, Study Versions, Documents, Exports, Audit Trail, Study Team, Study Settings
BuildBuild (dashboard), Corrections, Amendment, Saves, Forms, Visit Schedule, Visit and Form Mapping, AI Workstation, Form builder
UAT and LiveDashboard, 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 onlyIssues, Results
Live onlySite Team, Reports: Lock readiness
Where: Study overview. Role: Project Manager.

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

Quality and oversight

Every permission this role holds

42 permissions (template version 7).

PermissionWhat it allowsHeld atRiskConstraint
user.directory.readBrowse the organization user directory (for team staffing)organization, studystandard
ai.generateGenerate or edit forms with AIorganization, studystandard
audit.readAccess audit trailorganization, study, sitestandard
document.readView, download, and preview study documentsorganization, study, sitestandard
document.writeUpload documents, add versions, edit metadataorganization, studystandard
document.manageApprove and archive study documentsorganization, studystandard
export.readView export historyorganization, studystandard
export.runTrigger ad-hoc and signed exportsorganization, studycritical
form.readOpen forms and view answersorganization, study, sitestandard
form.designEdit form templates in builderorganization, studystandard
form.publishPublish form versions to liveorganization, studystandard
form.freezeMarks a role as data-locking authority (separation of duties: cannot also enter data)organization, studystandardseparation of duties (enter-vs-lock)
sdv.configureDefine the SDV / risk-based targeting plan (which fields require source verification)organization, studystandard
clinical.query.readView queriesorganization, study, sitestandard
clinical.query.raiseOpen a new manual queryorganization, studystandardseparation of duties (query-raise-vs-answer)
clinical.event.readRead a subject’s events and the adverse event and SAE logsorganization, study, sitestandard
clinical.event.reportSet the safety report status of a serious adverse event and its awareness timeorganization, study, sitestandard
clinical.event.reconcileRecord the reconciliation of a serious adverse event with the safety databaseorganization, studystandard
deviation.reportReport and update protocol deviation statusorganization, study, sitestandard
site.readView site detailsorganization, study, sitestandard
site.writeCreate / edit sites and stafforganization, studystandard
site.activateActivate a registered siteorganization, studyelevated
site.transitionTransition site lifecycle (suspend / resume / close)organization, studyelevated
study.readView study details and dashboardsorganization, study, sitestandard
study.writeEdit study settings and teamsorganization, studystandard
study.state.changeHold, resume, close to enrollment and complete a studyorganization, studyelevatedseparation of duties (enter-vs-lock)
study.lockLock and unlock the study database (two different people, each with an e-signature)organization, studycriticalneeds an e-signature; separation of duties (enter-vs-lock)
subject.readView subject dataorganization, study, sitestandard
team.assignAssign / provision a study team roleorganization, studyelevated
team.manageSuspend / resume / retire team assignmentsorganization, studyelevated
team.training_completeMark a team member as protocol-training completeorganization, studystandard
study.version.readView the study's versions: the version list, UAT cycles, sign-offs and the changes between versionsorganization, studystandard
study.amendment.startStart an amendment (the next version of a Live study)organization, studyelevated
study.version.submit_uatSubmit a version in Build to UAT (freezes its design and opens a UAT cycle)organization, studyelevated
study.uat.close_cyclePass or fail the open UAT cycle (a failed cycle returns the version to Build)organization, studyelevated
study.uat_issue.readView the issues and results of a UAT cycle (what testers found, and what became of it)organization, study, sitestandard
study.uat_issue.writeRaise, edit, resolve, accept and reopen the issues of the open UAT cycleorganization, study, sitestandard
study.version.signoffSign off a version that passed UAT (author, QA or approver; three different people)organization, studycriticalneeds an e-signature
study.version.go_liveTake an approved version Live (supersedes the version that was Live)organization, studycritical
study.version.withdrawWithdraw a version that has not gone Liveorganization, studyelevated
visit.readView visit schedule and dataorganization, study, sitestandard
workflow.designBuild and edit workflowsorganization, studyelevated

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.

Where: Live workspace > Dashboard. Role: Project Manager.

Compliance Q&A

Compliance Q&ABuiltPart 11 11.10(a)Part 11 11.10(g)Annex 11 4Annex 11 10ICH E6 computerised-systems
Is the release of a validated configuration approved by independent people, and by whom?

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)

Compliance Q&ABuiltPart 11 11.10(g)Annex 11 12ICH E6 investigator-oversightALCOA+ original
Can the person who runs the study alter the data it collects?

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

Create a study · Staff a study team · Review and release a study · Open a site · Close and lock a study · Who can and cannot