This document describes the most important features of Management Portal for related user roles.
| Table of Contents | ||||
|---|---|---|---|---|
|
User Guide for System Admin
...
Enter project details (e.g. name of study, selection of data source types used in study) and click Save.
...
Properties | Description |
|---|---|
Project Id | A unique identifier of a project, study, or trial. This field is case-sensitive and is used across the platform to identify Management Portal users, participants and data submitted collected in the platform. |
Human readable project name | An optional project name that can be easily understandable to the users. |
Description | A brief description of the study. |
Location | The location where the study is conducted. |
Start date | Start date of the study. This information is collected only as meta-data. It is not used for any other validation in the system |
End date | End date of the study. This information is collected only as meta-data. It is not used for any other validation in the system |
Source Type | A list of source-types that can be used in the project. E.g., ANDROID_PHONE_1.0.0. |
Attributes | Additional meta-data of the study. This information is stored as a key-value pair. The Management Portal supports some predefined attributes that are available in the drop-down. Values should be entered manually by the user who is creating or managing the project. E.g., External-project-id: Enter project-id from Redcap. Supported attributes: Privacy-policy-url: Override default privacy-policy used on the |
pRMT app with a custom one for this project. Work-package: identifier to group a number of projects as belonging to the same team. Phase: if multiple Management Portal projects are created for the same study in different phases, specify the phase here. External-project-url: URL of the external project ID. |
Managing users
List of roles in Management Portal
Role | Project specific/Global | Description |
SYSTEM_ADMIN | Global | A user with SYSTEM_ADMIN role can create projects and users. Can access and manage all projects and resources attached to the project. Can access and manage OAuth Clients. Can access audit logs and health metrics. |
PROJECT_ADMIN | Project specific | A user with PROJECT_ADMIN role can access projects that are related to their role. Can create participants in a project. Can edit properties of a project. Can assign or remove data sources to participants in a project. E.g., apps and devices. |
PARTICIPANT | Project specific | Can send data from assigned (data)sources. All active Subjects created in Management Portal have PARTICIPANT role. User with PARTICIPANT role cannot login to Management Portal. |
INACTIVE_PARTICIPANT | Project specific | This role will be assigned to deactivated Subjects in a project. Their ability to send data will be deactivated once the latest access token expires. |
| Info |
|---|
The Management Portal user interface supports only SYSTEM_ADMIN and PROJECT_ADMIN roles. The PARTICIPANT and INACTIVE_PARTICIPANT roles are supported by Management Portal, but these user types do not interact directly with the portal application. The PROJECT_OWNER, PROJECT_AFFILIATE and PROJECT_ANALYST roles are not fully developed and should not be used. |
...
Enter user details and click on the Save button.
...
Properties | Description |
Login | The username of the user. |
First name | First name of the user. |
Last name | Last name of the user. |
Email address of the user where the activation link will be sent. | |
Role | Role “ROLE_SYS_ADMIN” will be already defined for this user. |
2. Creating a user with PROJECT_ADMIN role
...
Enter user details and add project specific roles, click on the Save button. (Please note only PROJECT-ADMIN and SYSTEM-ADMIN users are fully supported by Management Portal web interface at the moment.)
...
Properties | Description |
Login | The username of the user. |
First name | First name of the user. |
Last name | Last name of the user. |
Email address of the user where the activation link will be sent. | |
Role | Select a combination of an Authority (here “ROLE_PROJECT_ADMIN”) and a project. From the drop-downs and press on the “Add” button to add it to the Role list. When not pressing “Add”, the role assignment will not be saved. |
3. Resend activation link
...