From 8409ccc5190ee18f511762d77e0d6297f36f2e5f Mon Sep 17 00:00:00 2001 From: TiG Date: Thu, 11 Mar 2021 18:16:11 +0100 Subject: [PATCH 1/3] split up consent part and minor changes in text --- source/guides/consent-management.rst | 41 ++++++++++++++++------------ 1 file changed, 24 insertions(+), 17 deletions(-) diff --git a/source/guides/consent-management.rst b/source/guides/consent-management.rst index a682336..9d7fbc6 100644 --- a/source/guides/consent-management.rst +++ b/source/guides/consent-management.rst @@ -3,8 +3,8 @@ Upload a consent document ========================= -Upload the new document ------------------------ +Upload a new document +--------------------- 1. Click on **Admin** on the front page 2. Go to **Consent documents** @@ -35,29 +35,36 @@ The legal basis for each subject can be found in the subject detail view. .. _subject-consent: -Set subject consent -=================== +Set Recruitment Consent for a Subject +===================================== + +1. In subject management > subject details, go to the **Data protection** tab. + +2. Click on the checkbox **Recruitment consent**. It will not be checked + immediately. Instead it indicates that you are waiting for confirmation + from the subject. + +3. If the subject agrees, click on **Confirm**. + +4. If the subject rejects the request, clear the checkbox. + + +.. _subject-consent-maintenance: + +Maintain Recruitment Consents +============================= To get an overview of all subjects for whom a new **Recruitment consent** is required, proceed as follows: 1. Click on **Subjects** on the front page -2. Go to **Maintenance** (blue button) +2. Go to **Maintenance** 3. Choose the **Consent** tab. You will see a list of all subjects with outdated recruitment consents. -4. Click on **Details** (opens in new tab). - -Once you have found a subject for which you want to set consent: - -1. In subject management, go to the **Data protection** tab. - -2. Click on the checkbox **Recruitment consent**. It will not be checked - immediately. Instead it indicates that you are waiting for confirmation - from the subject. - -3. If the subject agrees, click on **Confirm**. +4. Click on **Details** of a listed subject (opens in new browser tab) -4. If the subject rejects the request, clear the checkbox. +Refer to :ref:`subject-consent` once you have found a subject for which you +want to set consent. -- GitLab From 5a47a4143c08db790f5a0763b44860d63be6ada3 Mon Sep 17 00:00:00 2001 From: Tobias Bengfort Date: Mon, 15 Mar 2021 16:26:19 +0100 Subject: [PATCH 2/3] rm trailing periods in lists --- source/guides/consent-management.rst | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/source/guides/consent-management.rst b/source/guides/consent-management.rst index 9d7fbc6..d03dd49 100644 --- a/source/guides/consent-management.rst +++ b/source/guides/consent-management.rst @@ -4,7 +4,7 @@ Upload a consent document ========================= Upload a new document ---------------------- +----------------------- 1. Click on **Admin** on the front page 2. Go to **Consent documents** @@ -24,30 +24,28 @@ case there is a two step process: 1. Mark the old consent document as **deprecated**. The document is still considered valid but subjects who have agreed to this document will show up - in the consent maintenance view (see below). + in the consent maintenance view (see below) 2. Mark the old consent document as **invalid**. Now all consents related to this document are void. Subjects who have not been updated to the new document are no longer available for recruitment and will potentially show - up in the data protection dashboard. + up in the data protection dashboard The legal basis for each subject can be found in the subject detail view. - .. _subject-consent: Set Recruitment Consent for a Subject ===================================== -1. In subject management > subject details, go to the **Data protection** tab. +1. In subject management > subject details, go to the **Data protection** tab 2. Click on the checkbox **Recruitment consent**. It will not be checked immediately. Instead it indicates that you are waiting for confirmation - from the subject. - -3. If the subject agrees, click on **Confirm**. + from the subject -4. If the subject rejects the request, clear the checkbox. +3. If the subject agrees, click on **Confirm** +4. If the subject rejects the request, clear the checkbox .. _subject-consent-maintenance: @@ -62,7 +60,7 @@ required, proceed as follows: 2. Go to **Maintenance** 3. Choose the **Consent** tab. You will see a list of all subjects with - outdated recruitment consents. + outdated recruitment consents 4. Click on **Details** of a listed subject (opens in new browser tab) -- GitLab From 0f056cd24d674640f711cd4c53b3962ca55d9b1b Mon Sep 17 00:00:00 2001 From: Tobias Bengfort Date: Mon, 15 Mar 2021 16:26:31 +0100 Subject: [PATCH 3/3] Revert "rm trailing periods in lists" This reverts commit 5a47a4143c08db790f5a0763b44860d63be6ada3. --- source/guides/consent-management.rst | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/source/guides/consent-management.rst b/source/guides/consent-management.rst index d03dd49..9d7fbc6 100644 --- a/source/guides/consent-management.rst +++ b/source/guides/consent-management.rst @@ -4,7 +4,7 @@ Upload a consent document ========================= Upload a new document ------------------------ +--------------------- 1. Click on **Admin** on the front page 2. Go to **Consent documents** @@ -24,28 +24,30 @@ case there is a two step process: 1. Mark the old consent document as **deprecated**. The document is still considered valid but subjects who have agreed to this document will show up - in the consent maintenance view (see below) + in the consent maintenance view (see below). 2. Mark the old consent document as **invalid**. Now all consents related to this document are void. Subjects who have not been updated to the new document are no longer available for recruitment and will potentially show - up in the data protection dashboard + up in the data protection dashboard. The legal basis for each subject can be found in the subject detail view. + .. _subject-consent: Set Recruitment Consent for a Subject ===================================== -1. In subject management > subject details, go to the **Data protection** tab +1. In subject management > subject details, go to the **Data protection** tab. 2. Click on the checkbox **Recruitment consent**. It will not be checked immediately. Instead it indicates that you are waiting for confirmation - from the subject + from the subject. + +3. If the subject agrees, click on **Confirm**. -3. If the subject agrees, click on **Confirm** +4. If the subject rejects the request, clear the checkbox. -4. If the subject rejects the request, clear the checkbox .. _subject-consent-maintenance: @@ -60,7 +62,7 @@ required, proceed as follows: 2. Go to **Maintenance** 3. Choose the **Consent** tab. You will see a list of all subjects with - outdated recruitment consents + outdated recruitment consents. 4. Click on **Details** of a listed subject (opens in new browser tab) -- GitLab