From 37004d8f50def410e35d5781aae76b04952e4d0b Mon Sep 17 00:00:00 2001
From: Nils Berge <60594671+nils-work@users.noreply.github.com>
Date: Wed, 29 Nov 2023 15:53:55 +1100
Subject: [PATCH 1/3] Added Data Holder Dashboards section

Addresses: https://github.com/ConsumerDataStandardsAustralia/standards/issues/334
---
 slate/source/includes/_cx_standards.md.erb         |  1 +
 slate/source/includes/cx_standards/dashboards.md   | 14 ++++++++++++++
 .../releasenotes/releasenotes.1.29.0.html.md       |  3 ++-
 3 files changed, 17 insertions(+), 1 deletion(-)
 create mode 100644 slate/source/includes/cx_standards/dashboards.md

diff --git a/slate/source/includes/_cx_standards.md.erb b/slate/source/includes/_cx_standards.md.erb
index a78377756..d81cabafd 100644
--- a/slate/source/includes/_cx_standards.md.erb
+++ b/slate/source/includes/_cx_standards.md.erb
@@ -5,4 +5,5 @@
 <%= partial "includes/cx_standards/authorisation.md" %>
 <%= partial "includes/cx_standards/amending_authorisation.md" %>
 <%= partial "includes/cx_standards/notifications.md" %>
+<%= partial "includes/cx_standards/dashboards.md" %>
 <%= partial "includes/cx_standards/withdrawals.md" %>
diff --git a/slate/source/includes/cx_standards/dashboards.md b/slate/source/includes/cx_standards/dashboards.md
new file mode 100644
index 000000000..7e166b3a8
--- /dev/null
+++ b/slate/source/includes/cx_standards/dashboards.md
@@ -0,0 +1,14 @@
+<h2 class="schema-heading" id="consumer-experience_dashboard-standards">Dashboard Standards</h2>
+
+```diff
+Added Dashboard Standards section
+```
+
+This section outlines standards for consumer dashboards. These are expected to be implemented on each specific data sharing arrangement.
+
+<h3 class="schema-toc" style="margin-top:2.5em;border-top:0;font-size:15px;" id="consumer-experience_dashboard-standards_data-holder-dashboards">Data Holder Dashboards</h3>
+
+|Area|CX Standard|
+|-------------------|------------------------------|
+|**Data Holder Dashboard:**<br>Amending authorisation details|When a consumer amends an authorisation in accordance with rule 4.22A, which is linked to a _cdr_arrangement_id_ supplied by the data recipient as per the [amending authorisation standards](#amending-authorisation-standards), data holders **MUST** display the details of each authorisation’s amendment on the consumer’s dashboard.<br><br>**Note:** this requirement gives effect to rule 1.15(3)(h)|
+|**Data Holder Dashboard:**<br>Data recipient handling details|Data holders **MUST** advise consumers to check with the relevant data recipient for information about how their data may be handled.<br><br>The precise wording of this message is at the discretion of the data holder. The data holder **MAY** consider using or paraphrasing the following message:<br><ul><li><i>‘You should check with [ADR brand/the data recipient] for more information on how they are handling your data, and for any other permissions you may have given them. See [ADR]’s CDR policy or their Dashboard for more information.’</i><ul>|
diff --git a/slate/source/includes/releasenotes/releasenotes.1.29.0.html.md b/slate/source/includes/releasenotes/releasenotes.1.29.0.html.md
index 5e38280e2..387ba37a0 100644
--- a/slate/source/includes/releasenotes/releasenotes.1.29.0.html.md
+++ b/slate/source/includes/releasenotes/releasenotes.1.29.0.html.md
@@ -27,7 +27,7 @@ This release addresses the following change requests raised on [Standards Mainte
 
 This release addresses the following Decision Proposals published on [Standards](https://github.com/ConsumerDataStandardsAustralia/standards/issues):
 
-- [Decision Proposal xxx - Description](https://github.com/ConsumerDataStandardsAustralia/standards/issues/xxx)
+- [Decision Proposal 334 - Data Holder Dashboards](https://github.com/ConsumerDataStandardsAustralia/standards/issues/334)
 
 ## General Changes
 |Change|Description|Link|
@@ -64,6 +64,7 @@ This release addresses the following Decision Proposals published on [Standards]
 
 |Change|Description|Link|
 |------|-----------|----|
+|Dashboard Standards|**[Decision Proposal #334](https://github.com/ConsumerDataStandardsAustralia/standards/issues/334):** Added Dashboard Standards section to include detail for Data Holder Dashboards|[Dashboard Standards](../../#consumer-experience_dashboard-standards)|
 
 ## Non-Functional Requirements
 

From 76b6fa6f3dc1e554020aa8eda80a9a374b84351e Mon Sep 17 00:00:00 2001
From: Nils Berge <60594671+nils-work@users.noreply.github.com>
Date: Thu, 30 Nov 2023 10:40:56 +1100
Subject: [PATCH 2/3] Updated with data attribute

---
 slate/source/includes/cx_standards/dashboards.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/slate/source/includes/cx_standards/dashboards.md b/slate/source/includes/cx_standards/dashboards.md
index 7e166b3a8..409c10dea 100644
--- a/slate/source/includes/cx_standards/dashboards.md
+++ b/slate/source/includes/cx_standards/dashboards.md
@@ -6,7 +6,7 @@ Added Dashboard Standards section
 
 This section outlines standards for consumer dashboards. These are expected to be implemented on each specific data sharing arrangement.
 
-<h3 class="schema-toc" style="margin-top:2.5em;border-top:0;font-size:15px;" id="consumer-experience_dashboard-standards_data-holder-dashboards">Data Holder Dashboards</h3>
+<h3 class="schema-toc" data-cds-menu="h3" id="consumer-experience_dashboard-standards_data-holder-dashboards">Data Holder Dashboards</h3>
 
 |Area|CX Standard|
 |-------------------|------------------------------|

From 7e8843f68eb715d217f04d5d6e50444d0ed63272 Mon Sep 17 00:00:00 2001
From: Nils Berge <60594671+nils-work@users.noreply.github.com>
Date: Thu, 30 Nov 2023 14:32:29 +1100
Subject: [PATCH 3/3] Added FDO details

---
 slate/source/includes/cx_standards/dashboards.md | 4 ++--
 slate/source/includes/introduction/_fdo.md       | 5 +++++
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/slate/source/includes/cx_standards/dashboards.md b/slate/source/includes/cx_standards/dashboards.md
index 409c10dea..4ec9d9078 100644
--- a/slate/source/includes/cx_standards/dashboards.md
+++ b/slate/source/includes/cx_standards/dashboards.md
@@ -10,5 +10,5 @@ This section outlines standards for consumer dashboards. These are expected to b
 
 |Area|CX Standard|
 |-------------------|------------------------------|
-|**Data Holder Dashboard:**<br>Amending authorisation details|When a consumer amends an authorisation in accordance with rule 4.22A, which is linked to a _cdr_arrangement_id_ supplied by the data recipient as per the [amending authorisation standards](#amending-authorisation-standards), data holders **MUST** display the details of each authorisation’s amendment on the consumer’s dashboard.<br><br>**Note:** this requirement gives effect to rule 1.15(3)(h)|
-|**Data Holder Dashboard:**<br>Data recipient handling details|Data holders **MUST** advise consumers to check with the relevant data recipient for information about how their data may be handled.<br><br>The precise wording of this message is at the discretion of the data holder. The data holder **MAY** consider using or paraphrasing the following message:<br><ul><li><i>‘You should check with [ADR brand/the data recipient] for more information on how they are handling your data, and for any other permissions you may have given them. See [ADR]’s CDR policy or their Dashboard for more information.’</i><ul>|
+|**Data Holder Dashboard:**<br>Amending authorisation details|**Effective from July 1st 2024:**<br><br>When a consumer amends an authorisation in accordance with rule 4.22A, which is linked to a _cdr_arrangement_id_ supplied by the data recipient as per the [amending authorisation standards](#amending-authorisation-standards), data holders **MUST** display the details of each authorisation’s amendment on the consumer’s dashboard.<br><br>**Note:** this requirement gives effect to rule 1.15(3)(h)|
+|**Data Holder Dashboard:**<br>Data recipient handling details|**Effective from July 1st 2024:**<br><br>Data holders **MUST** advise consumers to check with the relevant data recipient for information about how their data may be handled.<br><br>The precise wording of this message is at the discretion of the data holder. The data holder **MAY** consider using or paraphrasing the following message:<br><ul><li><i>‘You should check with [ADR brand/the data recipient] for more information on how they are handling your data, and for any other permissions you may have given them. See [ADR]’s CDR policy or their Dashboard for more information.’</i><ul>|
diff --git a/slate/source/includes/introduction/_fdo.md b/slate/source/includes/introduction/_fdo.md
index 47e519f57..baeb63d38 100644
--- a/slate/source/includes/introduction/_fdo.md
+++ b/slate/source/includes/introduction/_fdo.md
@@ -1,5 +1,9 @@
 ## Future Dated Obligations
 
+```diff
+Added Data Holder Dashboards Future Dated Obligation
+```
+
 The standards, as published from time to time, may include specific statements indicating that a specific section of the standards will not take effect until a future date or may cease to have effect on some future date.
 
 The table below highlights these areas of the standards.
@@ -30,3 +34,4 @@ The table below highlights these areas of the standards.
 |[Get Scheduled Payments For Specific Accounts V2](#get-scheduled-payments-for-specific-accounts)|<ul><li>Data Holders **MUST** implement v2 of this endpoint by **March 11th 2024**</li><li>Data Holders **MAY** retire v1 of this endpoint from **September 9th 2024**</li></ul> | March 11th 2024 |
 |[Get Metrics V3](#get-metrics)|<ul><li>Data Holders **MAY** retire v3 of this endpoint by the earlier of **13th May 2024** or when the ACCC announce that this version is no longer being called</li><li>Data Holders going live on, or after, 1st November 2023 are not required to support this version</li></ul>| May 13th 2024 |
 |[Get Metrics v5](#get-metrics)|<ul><li>Data Holders **MUST** implement v5 of this endpoint by **May 13th 2024**</li><li>Data Holders **MAY** deprecate v4 of this endpoint once v5 is implemented</li></ul>| May 13th 2024 |
+|[Data Holder Dashboards](#consumer-experience_dashboard-standards_data-holder-dashboards)|Data Holders **MUST** implement the following CX Standards by **July 1st 2024**<ul><li>Data Holder Dashboard: Amending authorisation details<li>Data Holder Dashboard: Data recipient handling details</ul>| July 1st 2024 |