These guidelines provide examples for how to implement the authorisation flow for common scenarios.
Overview
This example of the authorisation process covers account selection and confirmation for individual accounts.
Wireframes and guidelines
Note: The wireframes shown are examples of how to implement key rules, standards, and guidelines. Use the on-screen functions to adjust zoom level or expand the wireframes to be viewed at full screen.
Default example
The following wireframes show a basic example of the authorisation process. Variations can be found in the below sections.
Unavailable accounts
An account may be considered unavailable for various reasons. Unavailable accounts may include eligible accounts that can’t be shared — for example, to prevent financial harm or because the account user doesn’t have sharing rights.
Unavailable accounts may also include ineligible accounts, or accounts that are not captured under the required consumer data rules. Data holders may show these accounts as unavailable to reduce confusion, such as where a consumer expects to see certain accounts, but cannot select them as they’re not eligible to be shared. While certain account or product types are excluded from the required consumer data rules, data holders may choose to share these accounts voluntarily.
The following wireframes show examples of the account selection step when a consumer has accounts unavailable for data sharing.
All accounts can be shown
Unavailable accounts cannot be shown
No accounts can be shown
Data related to one or no accounts
The following wireframes show an example of authorisation when the consumer only has one account and an example of when data does not relate to any accounts (e.g. saved payees).
Selection functionality
The following wireframes show an example of authorisation with:
- a profile selection step; and
- additional functionality to support account discovery and selection where further navigation or interaction is required to view all accounts.
Duration
The following wireframes show examples where authorisation is being sought for disclosure on a single occasion and for ongoing collection.
Layout variation
The CX Guidelines demonstrate extensive requirements for completeness. CX research suggests that breaking content into several steps facilitates comprehension and usability.
The following wireframes suggest alternative patterns for the authorisation.
Cancellation
The following wireframes show an example of cancelling authorisation.
Download open source asset
Open source design assets are created in Figma for the purposes of assisting implementation. This Figma file contain annotated wireframes and working prototypes for Authorisation to disclose, including:
- Default example
- Unavailable accounts
- All accounts can be shown
- Unavailable accounts cannot be shown
- No accounts can be shown
- Data related to one or no accounts
- Selection functionality
- Duration
- Layout variation
- Cancellation
Item | File | Date released | Version introduced |
|---|---|---|---|
3AU. Authorisation to disclose v1.35.0.2025.09.24.fig | Sep 24, 2025 | 1.35.0 |
For past versions, refer to Change log.
About this page
References
The artefacts on this page were informed by the following sources.
Title | Author | Date published | URL | Type |
|---|---|---|---|---|
Data Standards Body (DSB) | Jun 19, 2025 | github.com | Consultations | |
Data Standards Body (DSB) | Jun 6, 2025 | github.com | Consultations | |
Data Standards Body (DSB) | Jun 5, 2025 | github.com | Consultations | |
Data Standards Body (DSB) | Apr 15, 2025 | cdr-support.zendesk.com | Guidance | |
Data Standards Body (DSB) | Apr 15, 2025 | github.com | Consultations | |
Data Standards Body (DSB) | Apr 4, 2025 | github.com | Consultations | |
Data Standards Body (DSB) | Mar 14, 2025 | github.com | Consultations | |
Data Standards Body (DSB) | Dec 18, 2024 | github.com | Consultations | |
Data Standards Body (DSB) | Aug 12, 2024 | github.com | Consultations | |
Data Standards Body (DSB) | Jun 28, 2024 | cdr-support.zendesk.com | Guidance | |
Data Standards Body (DSB) | Jan 24, 2023 | github.com | Consultations | |
Data Standards Body (DSB) | Feb 9, 2021 | github.com | Consultations | |
Data Standards Body (DSB) | Jan 29, 2021 | github.com | Consultations | |
Office of the Australian Information Commissioner (OAIC) | Aug 1, 2020 | miro.com | Consultations | |
Data Standards Body (DSB) | May 21, 2020 | github.com | Consultations | |
GippsTech | Jul 31, 2019 | cx.dsb.gov.au | Research | |
Greater than X | Jul 31, 2019 | cx.dsb.gov.au | Research | |
Tobias | Jul 31, 2019 | cx.dsb.gov.au | Research | |
Tobias | Feb 28, 2019 | cx.dsb.gov.au | Research | |
Data Standards Body (DSB) | Jan 1, 2019 | consumerdatastandardsaustralia.github.io | Guidance | |
Nielsen Norman Group (NNG) | Apr 24, 1994 | nngroup.com | Other | |
Nielsen Norman Group (NNG) | Apr 24, 1994 | nngroup.com | Other | |
Nielsen Norman Group (NNG) | Apr 24, 1994 | nngroup.com | Other | |
Nielsen Norman Group (NNG) | Apr 24, 1994 | nngroup.com | Other |
Last updated
This page was updated @Sep 24, 2025
Have your say
Community consultations and maintenance are part of our ongoing process. Here’s how you can get involved:
- Request new Guidelines or changes to existing Guidelines through the CX Guidelines Consultation process
- Request new Standards or changes to existing Standards through the Standards Maintenance process
- Log a ticket for any questions about the rules, standards, or guidelines through the CDR Support Portal
- Email your feedback to cx@dsb.gov.au
Quick links to CX Guidelines:
→ cx@dsb.gov.au → cx.dsb.gov.au | cds.gov.au