Dp/334

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" %>

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" data-cds-menu="h3" id="consumer-experience_dashboard-standards_data-holder-dashboards">Data Holder Dashboards</h3>
+
+|Area|CX Standard|
+|-------------------|------------------------------|
+|**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>|

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,6 +34,7 @@ The table below highlights these areas of the standards.
 |[Get Scheduled Payments For Specific Accounts V2](#cdr-banking-api_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](#cdr-admin-api_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](#cdr-admin-api_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 |
 |[Get Billing For Account](#cdr-energy-api_get-billing-for-account)|Data Holders **MAY** retire v2 of this endpoint by **September 9th 2024** if they implement v3| September 9th 2024 |
 |[Get Bulk Billing](#cdr-energy-api_get-bulk-billing)|Data Holders **MAY** retire v2 of this endpoint by **September 9th 2024** if they implement v3| September 9th 2024 |
 |[Get Billing For Specific Accounts](#cdr-energy-api_get-billing-for-specific-accounts)|Data Holders **MAY** retire v2 of this endpoint by **September 9th 2024** if they implement v3| September 9th 2024 |

slate/source/includes/releasenotes/releasenotes.1.29.0.html.md

@@ -30,6 +30,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 334 - Data Holder Dashboards](https://github.com/ConsumerDataStandardsAustralia/standards/issues/334)
 - [Decision Proposal 333 - Business Consumer Provisions](https://github.com/ConsumerDataStandardsAustralia/standards/issues/333)
 
 ## General Changes
@@ -72,6 +73,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)|
 |Business Consumer Provisions|**[Decision Proposal #333](https://github.com/ConsumerDataStandardsAustralia/standards/issues/333):** Updated requirements for Business consumer statements and Business consumer disclosure consents|[Consent Standards](../../#consent-standards)|
 
 ## Non-Functional Requirements