Australian Government Digital ID System (AGDIS)

Key Roles in the AGDIS Workflow

The following example explains how the workflow may operate where John is the individual, AuthNTick is the relying party, and Alice manages business authorisations through RAM.

• The User: John is the individual who wants to complete an online identity verification or background screening process.
• The Relying Party: AuthNTick is the service provider that requests verified identity attributes so it can provide a background screening service.
• The Digital ID Provider: A provider such as myID helps John prove and manage his Digital ID.
• The Identity Exchange: The exchange facilitates secure information flow between the Digital ID provider, attribute service providers and the relying party.
• The Business Authorisation Manager: Alice may use the Relationship Authorisation Manager (RAM) to authorise John to act on behalf of a business.

Step 1: John Starts the Verification Request

John visits AuthNTick to complete a background screening check, such as a Nationally Coordinated Criminal History Check or an employment screening check.

Instead of uploading scanned copies of his passport, driver licence or other identity documents, John selects an option such as Verify with Digital ID. This allows the identity verification process to occur through the Digital ID framework.

Step 2: AuthNTick Requests Only the Required Attributes

AuthNTick, as the relying party, requests only the identity attributes needed to complete the check. These may include details such as John's full name, date of birth and other required identity information.

This supports the principle of data minimisation. Rather than collecting and storing unnecessary raw identity documents, AuthNTick receives only the verified information required for the service.

Step 3: John Authenticates Through His Digital ID

John is redirected to authenticate using an accredited Digital ID provider, such as myID. The level of verification required depends on the service and the required identity strength.

• Standard identity strength: John may verify his identity using accepted identity documents and previously verified information.
• Strong identity strength: John may be required to complete additional verification, such as photo or biometric verification, depending on the provider and the service requirements.

The important point is that John authenticates through the Digital ID system, rather than repeatedly sending raw copies of identity documents to each service provider.

Step 4: Alice Manages Business Authorisation Through RAM

If John is completing the check on behalf of a company, a business authorisation step may be required. This is where RAM can be used.

Alice, as a principal authority or authorisation administrator for the business, can use RAM to authorise John to act on behalf of that business. This confirms that John has permission to access relevant online services or complete authorised tasks for the organisation.

For example, Alice may authorise John to manage screening tasks or share required business-related identity attributes for a specific organisation. This helps ensure that the person acting for the business has the correct authority to do so.

Step 5: John Gives Consent and Verified Data Is Released

Once John reviews the request and gives consent, the Digital ID system can send a secure response back to AuthNTick. This response may confirm verified identity attributes such as John's name and date of birth.

AuthNTick can then use the verified information to continue the background screening process without needing to store unnecessary copies of John's passport, driver licence or other sensitive identity documents.

Why This Matters for Background Screening

Using the Australian Government Digital ID System can make background screening safer, faster and more privacy-conscious. It reduces manual document handling, lowers the risk of identity document exposure and provides a more streamlined experience for applicants, employers and screening providers.

For organisations, this can improve compliance and reduce friction in onboarding workflows. For individuals, it provides a more secure way to prove who they are while sharing only the information required for the service.

Conclusion

AGDIS provides a modern framework for digital identity verification in Australia. In a background screening scenario, it allows a person like John to verify his identity through a trusted Digital ID provider, allows a relying party such as AuthNTick to receive only the required verified attributes, and allows business representatives such as Alice to manage authorisations through RAM where business access is required.

The result is a more secure, efficient and privacy-focused approach to identity verification for employment screening and related background check services.