For each registry, the registry coordinator is, as default, assigned as Access Manager who is managing the access rights to the DWH applications (In future a HD Entity Access Management (EAM) LIKE system to be foreseen).

In this process, access requests are analyzed, validated if legitimate and approved. The registry coordinator should consult their Data Protection Officer (DPO) for more in-depth information concerning the grating of access rights.

Two data user roles are distinguished:

• Data validator
  • should only access the DWH validation environment with the purpose of data validation. Analytical tasks are explicitly prohibited in the validation environment.
  • Access is limited to two individuals per registry, a primary and a backup

• Data analyst
  • should only access data in the DWH analysis environment with the purpose of data analysis
  • Multiple data users might request access to this analysis environment

Note:  It is acknowledged that, in some cases, the same individual may serve in both roles: Data validator and Data analyst. These roles will be supported by separate accounts with distinct access rights.

A user request is requested via a ticket of type ‘Request Access’  by completing the application form via the service portal: Jira Service Management (JSM) portal.

If the requestor is the registry coordinator or head of the service, we can consider this request as approved. In case the requestor is not the registry coordinator, an approval should be received from the registry coordinator/access manager for the requested roles

Note: access request to the validation environment can only be approved for max 2 data validators per registry.

Credentials will be generated by the DWH team and provided to the Data Validator/Data Analyst by the SD team before closing the SD (service desk) ticket.