Sites

A site is a research location where subjects are actually enrolled and data is entered. A site has a code, a name, and a status. Sites are managed on the Sites screen inside a study (/studies/{studyId}/sites): here they are activated and switched between the active and closed states.

For each site the table shows the code, name, status, and the number of subjects enrolled at that site.

0:000:00

The Sites screen: statuses, design versions and activation on a published version.

Publication unlocks activation

A site cannot be activated “into a void”: it is bound to a published design version. This is the same BUILD → CONDUCT boundary as launching the study — until there is a live design, there is nothing to activate against.

Publish a design version first

The Activate site button is unavailable until the study has at least one published version. Build and publish the design (see Publish and launch) — only then can you activate the first site.

Activating a site

Activation is the only way to bring a site into being: there is no separate “create” without activation in the product. When activating you provide a code, a name, and the published design version the site will run on (only published versions are offered in the list).

1. Click Activate site (requires the site.activate permission).

2. Enter the site code (for example, SITE-01) and the site name.

3. Choose the design version — only published versions are available; the newest one is preselected.

4. Confirm — the site appears in the table with status Active and can enroll subjects from that moment.

Different sites can be activated on different published versions — a normal situation during amendments, when some sites have already moved to a new version while others still run on the previous one.

Site statuses

1. Activeclose
2. Closed
   • reopenActive

The site lifecycle: active ↔ closed; closing and reopening take a reason and are audited.

Status	Meaning
Active	The site is live: subjects can be enrolled into it
Closed	Enrollment into the site is blocked; data stays available

Closing and reopening

An active site can be closed (the site.deactivate permission). Closing requires a reason and warns about the consequence: enrollment of new subjects into this site is blocked. Already enrolled subjects and their data are not lost — they remain fully available for review, cleaning, and signing.

A closed site does not enroll subjects

While a site is closed, an attempt to enroll a subject into it is rejected: enrollment happens only at active sites. This guards against accidentally enrolling subjects into a location that has already been stopped.

Closing is reversible: a site can be reopened — it becomes active again and can enroll subjects. Reopening is confirmed separately.

Permissions

• Site visibility matches visibility everywhere else in the interface — by study.read in the scope of the corresponding site. A monitor limited to their own locations sees only those.
• Activation is gated by site.activate, closing by site.deactivate. Buttons are not shown without the required permission, and the server re-checks access anyway (default deny).

Publish and launchHow to get the design to a published version that sites are activated on.

Enrolling subjectsEnrollment happens only at active sites — what follows activation.

Roles & accessHow grants and a site's scope decide who activates and closes locations.