Project privileges
llows multiple beneficiaries to collaborate together in the project as teams. There are two types of teams:
The AF users / Project managers - All users of this team are allowed to view/edit the AF and the contracting sections (For more details please see: Contracting).
Special privilege manage allow the user management of all the teams
Project partner team(s) - Set of users that collaborate together as work force for each partner
Partner teams only appear upon the project status is Approved and are recommended to be assigned before the project is set to Contracted. In the contracting section and the reporting section the Project partner team(s) shall have rights over their own dedicated section. For more details please see: Contracting , Creation of partner reports .
Sensitive data enables protection of person related data according to GDPR. Users with active flag are able to mark (and view) sensitive data in List of expenditures and Procurement section in Partner reports. For more details please see: Partner report List of expenditures and Partner report procurement.
GDPR flag can be configured for project partner users. Users with monitoring right in System privileges, who are assigned to a project can always see content marked as sensitive in the related partner report sections.
During the contracting phase control institutions are assigned. This is also flagged up to each partner team in the project privileges section. When a control institution is assigned the name of the controller organisation will show up instead of “No control institution assigned”. More details see: Assignment of control institutions
It is only possible to invite users who are already registered in the system. The only required parameter to identify the user is the respective Jems username (e-mail used to register in Jems). Upon successful invitation, the invited user will see the respective project in his Dashboard.
Project privileges are restricted to the level of a specific project - each project is an “isolated island”.
A user who is collaborator in many projects, can have distinct privileges in different projects.
Only users who can create/collaborate in projects are allowed to be invited, see below as example:
Setup
Project privileges is an optional functionality to programmes, the section can be limited or even deactivated via System privileges:
Collaborators (“Allow user to create/collaborate in projects..“) :
HIDE - The section is not accessible
VIEW - User can view only the project privileges
EDIT - User can view and possibly make changes in project privileges - In order to make changes it is still required to have manage privilege in a particular project.
Monitoring (“Allow user to monitor projects..“) :
HIDE - The section is not accessible
VIEW - User can view only the project privileges
EDIT - User can view and make changes in project privileges (e.g. Admin)
For the scenario where a user/role has both sections privileges ticked (e.g. Admin, as shown above can create projects and also monitor), the higher privilege will always prevail.
Privileges changes are only applied when the user(s) (logout and) login again.