# About User Roles and Permissions

Source: https://sites.veevavault.help/gr/sitevault/sv-administration/roles-perms/

SiteVault’s system of roles and permissions defines what a user can see and do within the platform. This page introduces the different levels of access, from the foundational System Role to specific Extended Permissions and Study Assignments. These elements work together with other settings to ensure users have the right level of access to documents and data.

[![Roles Pyramid](/gr/uploads/sitevault/images/help/sv-roles-perms-relationships.png) ](/gr/uploads/sitevault/images/help/sv-roles-perms-relationships.png)

For additional access guidance, download the [SiteVault Security Matrix](/gr/uploads/sitevault/downloads/SiteVault-Security-Matrix.pdf) or [SiteVault User Access Guide](/gr/uploads/sitevault/downloads/SiteVault-User-Access-Guide.pdf).

## Sites vs. Research Organizations: The Importance of User Context

SiteVault is structured to accommodate a single research site seeking a tool to organize its study materials or a larger organization requiring multiple SiteVault environments. Research organizations have multiple sites (or divisions/departments), each managing individual SiteVault environments to which the organization’s SiteVault provides oversight. Users have system roles at the research organization and site levels. Users requiring access at multiple sites can have different system roles at different sites.

Records for patients, products, or organizations, can be shared across all sites within an organization.

[![Roles and Permissions](/gr/uploads/sitevault/images/help/sv-org-site-access.png) ](/gr/uploads/sitevault/images/help/sv-org-site-access.png)

## System Roles

System roles define the **base level of access** at a site or research organization. System roles are assigned when an administrator [creates a user account](/gr/sitevault/sv-administration/staff-create/). Based on a user’s responsibilities across sites, a user may have different roles at different sites.

| **Level** | **Role** | **Description** |
| **Research Organization** | **Research Organization Administrator** | 
- _Note: For full access, Research Organization Administrators should also be assigned as Site Administrators at every site in their organization._
- Full access to all settings, data and functionality
- Create and manage user accounts for the entire research organization
- CTMS Enabled: Full access to all CTMS functionality for all studies within their organization

 |
| **Research Organization Staff** | 
- View access to research organization-level information
- CTMS Enabled: View study schedules for all assigned studies

 |
| **Research Organization External** | 
- System role for monitors, CRAs, or auditors
- No access to any research organization-level data and documents

 |
| **Site** | **Site Administrator** | 
- Full access to all settings, data and functionality
- Create and manage user accounts for the site
- CTMS Enabled: Full access to all CTMS functionality for all studies at their site

 |
| **Site Staff** | 
- View access to site-level information
- Assigned Studies: Create documents, manage study participants, and send eConsents
- CTMS Enabled: View CTMS information for assigned studies

 |
| **Site External** | 
- System role for monitors, CRAs, or auditors
- View access to site-level information
- Assigned Studies: View limited study-level documents and data

 |
| **Site Viewer (all studies)** | 
- Assigned Studies: Edit document fields, create new drafts of documents, and participate in relevant workflows

 |

## Extended Permissions

Extended permissions add flexibility to a user’s system role by granting additional access. These permissions are assigned when an administrator [creates](/gr/sitevault/sv-administration/staff-create/) or [edits](/gr/sitevault/sv-administration/staff-edit-site-perm/) a user account.

By assigning extended permissions to a Site Staff user, an administrator can delegate specific tasks for **all studies** at once. For example, assigning the **Study Document Management** extended permission allows a staff user to manage documents for every study in the system, and assigning **Study Schedule Design & Management** allows them to build schedules for all studies.

**Note:** Administrators can create and manage user system roles and extended permissions; these user administration tasks are not included in any extended permissions.

| **Level** | **Permission** | **Description** |
| **Research Organization** | **Patient & Participant Management** | Create/manage patient and participant data (including recruitment) across the research organization and its sites |
| **Site** | **Study Administration** | Create/manage studies, study data, and settings across all studies |
| **Study Document Management** | Create/manage study and study staff-related documents across all studies |
| **Site Document Management** | Create/manage site-level documentation for staff, IRB/IECs, labs, sponsors, and products across all studies |
| **Patient & Participant Management** | Create/manage patient and participant data (including recruitment) across all studies |
| **Study Schedule Design & Management (CTMS)** | Create/manage CTMS study schedule components across all studies |
| **Financial Management (CTMS)** | Create/manage CTMS study budget and manage financial information across all studies |

## Study Assignments

A [study assignment](/gr/sitevault/studies/assign-create/) gives a user access to a specific study and its documents. Users can only be assigned one Study Role per study. While SiteVault provides a standard list of study roles, please note that specifying roles outside of the Principal Investigator and Subinvestigator is not a regulatory requirement. Only the Principal Investigator and Subinvestigator roles impact workflow tasks; all other roles act purely as informational labels to help you organize your team.

| **Level** | **Roles** |
| **External** | Auditor/Inspector |
| Sponsor/CRO |
| **Site Staff** | Clinical Research Coordinator |
| Data Coordinator |
| Budgets & Contracts |
| Principal Investigator |
| Regulatory Coordinator |
| Research Nurse |
| Subinvestigator |
| Pharmacist |
| Other Non-Investigator |

## Additional Settings that Affect User Access and Permissions

Something as simple as a document’s lifecycle state can determine user visibility, but SiteVault also offers several more granular settings that provide an additional level of secure flexibility.

### Restricted Document Visibility

_Study-level option for site staff and external users, granted in study assignments_

The [Restricted](/gr/sitevault/sv-administration/restricted/) document functionality allows sites to limit document visibility to specific users assigned to the study. The feature is intended to be used for blinded/masked studies where certain documents (ex. randomization information) must remain hidden from the larger study staff. Restricting documents and staff is a two-step process that includes first marking individual study documents as _Restricted_ and then granting individual study staff members access to restricted documents. Only study staff members with access to restricted documents can view study documents marked as _Restricted_.

### External Users Granted Access to Site Documents

_Site-level option for external users_

A Monitor or an External User may request to access your site’s business process documents, such as standard operating procedures (SOPs), work instructions, or policy memos. These are stored in the Site eBinder, which is not visible to non-site staff users. However, you can [share these documents with Monitors/External Users](/gr/sitevault/monitoring/site-share-site-docs/) on an individual document basis. This is not a user setting; it is a document setting that is set through a user action. When you choose to share a document, the document is visible to all Monitors and External Users at your site.

### Accept and Complete Monitoring Issue Tasks

_Study-level option for site staff users, granted in study assignments_

When creating a [study team assignment](/gr/sitevault/studies/assign-create/) an administrator (or site staff with the Study Management extended permission) can select the _Monitoring Issue Recipient_ option to designate the user as responsible for reviewing monitoring issue notifications and completing any related tasks.