This guidance provide examples for how to implement express consent Attribute Service Providers (ASPs) in the Australian Government Digital ID System (AGDIS).
Disclaimer: This page contains draft content intended for internal agency use. It is not intended for public distribution or reference. The information may be incomplete, subject to change, and should not be considered final or formally endorsed.
Overview
When acting in its capacity as an Attribute Service Provider (ASP), the Relationship Authorisation Manager (RAM) must request express consent from the individual when they accept a Business Authorisation.
When asking an individual to give consent, an ASP must:
- ensure that the process for an individual to provide express consent, or to withdraw or vary that consent, is described in clear, simple and accessible terms; and
- meet other requirements within the the Digital ID rules and standards.
This section provides examples illustrating how the guidance may be implemented. It also includes design patterns based on best practices and user research which are are not mandatory requirements.
For additional explanation on consent related obligations, please refer to OAIC’s guidance on Express consent in Australia’s Digital ID System.
Wireframes and guidance
Note: The wireframes shown are examples of how to implement key rules, standards, and guidance. 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 ASP express consent as required by the Relationship Authorisation Manager (RAM).
[TBC]Download open source asset
Open sources design assets are created in Figma for the purposes of assisting implementation. This Figma file contains annotated wireframes and working prototypes for Attribute Service Provider (ASP) consent, including:
- Default example
[update filter options]For past versions, refer to .
About this page
References
The artefacts on this page were informed by the following sources. [update filter options]
Last updated
This page was updated @March 26, 2025
Note: This document provides general guidance only. It does not constitute legal or other professional advice and should not be relied on as a statement of the law. As this is only a guide, it may contain generalisations. We encourage participants to obtain their own professional advice to ensure they understand their obligations under the Digital ID framework.
Have your say
Community consultations and maintenance are part of our ongoing process. Here’s how you can get involved:
- Request new guidance or changes to existing guidance through the UX guidance 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 Digital ID Support Portal
- Email your feedback to cx@dsb.gov.au
