In this article:
What is the account claim micro-app?
Blink's account claim micro-app lets your employees claim their Blink user accounts using two personal identifiers, with no email address or phone number needed up front. This is designed for organisations that don't hold reliable contact details (phone numbers or email addresses) for their frontline, so direct invitations aren't an option.
It allows employees to look up and claim their Blink user account with one identifier (an employee ID or their surname) and and a secondary field (their surname or a custom profile field your organisation chooses - e.g. date of birth, badge number). An employee ID could be a payroll number, badge number, or another ID that is unique to each person.
Users can access the micro-app by scanning a QR code or opening a link. They locate their account by providing two pieces of information, get directed to download the Blink app if they don't have it yet, and then go through registration flow to complete their account setup and provide their contact details for future access.
Pre-requisites
User profiles must already exist in Blink before they can claim their account. Import them via a bulk update (spreadsheet upload) or a SCIM sync (Entra, Okta, and similar). The account claim flow is not compatible with users added individually through the admin panel.
Each user record must include the fields used in your claim flow (for example, employee ID and surname, or a custom field).
The account claim micro-app must be enabled for your organisation. Contact your Blink representative to get set up.
For guidance on bulk imports, check out this article.
Set up
The Blink team configures the account claim experience for your organisation. In order to set this up, confirm which two pieces of information employees will use to claim their account:
Lookup field: used to locate an unclaimed Blink user account. This can be their employee ID or their surname.
Verification field: used to confirm it's really them. This can be their surname or a custom profile field, such as date of birth, store number, or badge ID.
The default combination is employee ID and surname. If your organisation doesn't store surnames consistently, or uses a different identifier, ask the Blink team to configure the combination that matches your data.
A few things to keep in mind:
Both fields must be populated on your user records in Blink for matching to work, so check your data coverage before going live.
One custom field can be configured per organisation.
Organisations using the default employee ID plus surname flow don't need to change anything.
End user experience
Here's what your employees will see on a mobile device:
Scan the QR code (or open the claim link) provided by your organisation.
Enter your details. This is the two identifiers your organisation has chosen, for example employee ID plus surname, or surname plus date of birth. If using the generic link, enter your company code first.
Account found. Once the details match, Blink confirms the account and directs the user to the remaining registration steps.
Download the Blink app if it isn't already installed. The landing screen links to the correct app store automatically.
Verify and finish setup. The user enters their phone number, receives a one-time passcode (OTP) to verify it, and completes their account setup.
Confirm Terms of Service and access Blink. The user completes the registration process by accepting Terms of Service.
Troubleshooting:
Employees are unable to scan the QR code
If employees can’t scan the QR code with their device, you can invite them via a different activation route. Read more here.
Some employees don’t know their employee ID
An Admin can help the user find their employee ID by looking it up in the Admin portal under the user profile.
An employee didn’t receive their OTP code
They should select ‘tap to send again’ in the Blink app. For further troubleshooting please see: https://helpdesk.joinblink.com/en/articles/14171711-problems-signing-in-to-blink#h_no_otp