Role actions are the ‘building blocks’ for rolesRoles. Each role action facilitates discrete functionality, and they can be assembled into roles Roles which are assigned to users to perform operational functions.
...
Additionally, all Role Actions definitions can be reviewed using the ‘Role Action Overview’ modal, accessible to users when modifying an existing Role.
...
...
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Dashboard
Provides access to the study Dashboard.
The role action also supports blinding requirements where users are expected only access specific areas of the application, but not see the study dashboard. Under blinded scenarios, users would not be given the ‘Dashboard’ role action.
This role action is also necessary for users to also access the components in Volunteers > Dashboard.
Overwhelmingly, most ClinSpark users are granted this role action so they can access the study Dashboard and other associated study components.
Study Data
This activates the component menu item and allows access to basic features within Study > Data.
...
Study Data Save Annotations
...
Writeable Actions
Each role action is identified with a property to determine if it is Writable. This indicates whether or not the role action will allow the user to make a modification of data through the user interface. The context on what is writable is based on the role action, however generally, if the role action allows a user to add, edit, or remove data it is writable. Role Actions that are intended to only allow ‘read only’ or limited capabilities in a component are otherwise identified as not writable.
...
Table of Contents
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Dashboard
Provides access to the study Dashboard.
The role action also supports blinding requirements where users are expected only access specific areas of the application, but not see the study dashboard. Under blinded scenarios, users would not be given the ‘Dashboard’ role action.
This role action is also necessary for users to also access the components in Volunteers > Dashboard.
Overwhelmingly, most ClinSpark users are granted this role action so they can access the study Dashboard and other associated study components.
Study Data
This activates the component menu item and allows access to basic features within Study > Data.
...
Study Data Save Annotations
This role action was deprecated in ClinSpark version 1.4.0. It was previously related to the ability to add annotations to Item data from within the Study > Data component.
...
Volunteer screens and an AE is collected into an unscheduled study event; screening number is S100
Volunteer has a screen fail
Volunteer returns for a second screening visit, and is later enrolled under a different subject record; screening number is S101
This role action would allow a qualified user to associate the AE collected under S100 to S101
...
Study
...
Data Move Form Data
Introduced in version 23.3.
Allows a user to move a form's data into another site, subject, or study event.
Accessible via Study > Data component.
...
Study Lab Data
Activates component menu item. When browsing study data with lab results, role action is required to view results.
...
Activates component menu item, and allows users to perform study design import/export.
...
Approval Management
Allows users to manage approval requirements around study specific entities such as Activity Plans, ECG Interval Study Configurations, Eligibility Mappings, Informed Consents, Sample Paths, and Study Lab Panels.
...
API
This is a unique role action that is typically assigned to ‘system’ accounts. It allows a user to leverage certain ClinSpark web services (such as APIs). Integration applications must be configured with this role action..
...
Approval Management
Allows users to manage approval requirements around study specific entities such as Activity Plans, ECG Interval Study Configurations, Eligibility Mappings, Informed Consents, Sample Paths, and Study Lab Panels.
...
API
This is a unique role action that is typically assigned to ‘system’ accounts. It allows a user to leverage certain ClinSpark web services (such as APIs). Integration applications must be configured with this role action.
Administration Users View API Tokens
Introduced in version 23.3.
Allows for read-only access to API tokens on a ClinSpark user profile. It will allow users to see all existing API token attributes, except token value.
...
Administration Users Manage API Tokens
Introduced in version 23.3.
Allows for full access to API tokens, including the ability to add and modify existing tokens.
...
Correspondence Call
Allows a user to perform calls to volunteers. This role action impacts call functionality present within volunteer profiles and on calendar components.
...