The TrustID integration lets you send a candidate a Right to Work (RTW) check without leaving Pinpoint. TrustID emails the candidate an invitation, the candidate completes the check on TrustID, and the outcome comes straight back into Pinpoint - as a pass/fail status, a set of result fields, and the full TrustID report PDF.
You can send a check by hand from an application, or have Pinpoint send it automatically as part of a candidate's onboarding process. When it's part of onboarding, the results can also be written into the candidate's onboarding answers, so the Right to Work verdict and its expiry date live alongside the rest of their record.
This article covers the current TrustID integration. If your account still uses the earlier version - which reports only invited/completed and keeps the outcome inside the PDF - see Using the TrustID Integration. Your Pinpoint Customer Success contact can tell you which one you're on.
Before you start
Pinpoint switches this on for you. Ask your Customer Success contact to enable the TrustID integration for your account.
You'll need a TrustID API account. This is not the same as your TrustID web login - ask your TrustID account manager for API access.
To send a check and see its results you need the "Initiate an integrated background check" permission. To see results without being able to send checks, the "view the results of integrated background checks" permission is enough.
What you need from TrustID
Your TrustID account manager provides these five values. Pass them to your Pinpoint Customer Success contact, who will add them to the integration for you.
Value | What it is |
Username | Your organisation's TrustID API account username. Not an email address. |
Password | The password for that API account. |
API Key | Your TrustID API key. Issued per organisation, and separate from the username and password. |
Branch ID | The TrustID branch your checks should be created against. |
API Base URL | Which TrustID environment to use. Production for live checks. |
Ask TrustID to enable Right to Work on the branch you give us, and to turn on check-completion callbacks for it. Without those, invitations can be created but results never come back.
Sending a Right to Work check from an application
Open the candidate's application, click the Application Actions menu, and choose Send to TrustID.
The Send to TrustID panel opens with First Name, Last Name and Email already filled in from the application. Check the email address is the one the candidate should receive the invitation on, then click Submit.
TrustID emails the candidate a link to complete their Right to Work journey. Nothing else is needed from you until they've finished.
The check appears on the application's Background Checks tab straight away, marked Pending.
Seeing the result
When the candidate finishes their TrustID journey, Pinpoint updates the check automatically - there's nothing to refresh or chase.
The status on the check gives you the headline outcome:
What TrustID found | Status in Pinpoint | What it means |
Continuous right to work | Passed | Right to Work confirmed. No restriction, no follow-up needed. |
Time-limited right to work | Consider | Valid, but a re-check is due. The follow-up date is on the check. |
Rejected | Not eligible | The check did not pass. |
Photo didn't match the applicant | Not eligible | Rejected - possible imposter. This overrides a pass. |
Liveness check failed | Not eligible | Rejected - the liveness check didn't pass. This overrides a pass. |
Digital identity check failed | Not eligible | Rejected - the digital identity check didn't pass. This overrides a pass. |
Passed, but the photo match was unsure | Consider | Needs review - someone should confirm the match by eye. |
A check is never passed automatically on a status Pinpoint doesn't recognise; it's shown as Consider so a person can look at it.
Click the check's name to open Check Details. Alongside who requested it and when, you'll see:
Result - the plain-English headline, e.g. "Right to Work confirmed".
Right to Work status - TrustID's own status: Continuous, Time Limited or Rejected.
Did the Right to Work check pass? - the outcome, e.g. "Pass Conditional".
RTW scheme - Digital, Share Code or Conditional.
Which document type was used? and ID document expiry date.
Face match and liveness, plus a pass/fail line for each document assessment TrustID ran.
Where relevant, the Right to Work expiry date for a time-limited result, any notes, and any rejection reason.
Download Report - click Click here to download for the full TrustID report PDF.
A note on the report PDF
TrustID keeps a completed check's results for around 30 days. After that the download link stops working. If you need a lasting copy of the report, have it saved into Pinpoint automatically - see Keeping the report and the outcome in Pinpoint below.
Using TrustID in onboarding
You can make the Right to Work check part of a candidate's onboarding process, so the invitation is sent as soon as the candidate reaches that step rather than someone having to remember to send it.
Adding the step
In your onboarding process, add a step and choose the Background Check step type. On the Setup tab, give the step a Step Name and a Description - the description is what the candidate sees in their onboarding portal - then choose TrustID as the Provider.
You don't need to change anything else. The First Name, Last Name and Email fields default to the candidate's own details, as their helper text says; set them only if you want to send something different.
Can't see TrustID in the Provider list? The TrustID step has to be switched on for your account by Pinpoint before it appears there. Contact your Customer Success contact and they'll enable it.
When the candidate reaches that step, Pinpoint sends the TrustID invitation for you, and the check appears on their application exactly as it would if you'd sent it by hand.
Keeping the report and the outcome in Pinpoint
For checks sent by an onboarding step, Pinpoint can also write the results into the candidate's onboarding answers and file the report PDF as a document. This is worth doing because it:
makes the Right to Work outcome part of the candidate's onboarding record, where the rest of their data lives, and reportable through your questions' reporting names;
lets the outcome travel onwards - if you export to an HR system, onboarding answers can carry the Right to Work verdict and its expiry date with them;
keeps your own permanent copy of the report PDF, before TrustID's retention window closes.
This is set up with your Customer Success Manager. Tell them which result fields you want and where they should go, and they'll configure the mapping. Nothing is mapped by default.
The fields available to map are:
Field | Typical use |
Did the Right to Work check pass? | The headline verdict. |
Right to Work status | TrustID's own status: Continuous, Time Limited or Rejected. |
Which document type was used? | The name of the document TrustID checked. |
ID document expiry date | When the document itself expires. |
Expiry date of Right to Work | When a time-limited right to work must be re-checked. |
Any time limited notes | TrustID's notes on the check. |
Rejected notes | Why the check was rejected. |
TrustID report (PDF) | The full report, saved to a document question, the application's Documents tab, or the candidate's Documents tab. |
What your questions need
So the answers land where you expect, each destination question must be:
on the candidate's onboarding process - it doesn't have to be on the same step as the check, but it must be somewhere in the same process;
banked, and given a reporting name - without a reporting name it can't be mapped at all;
the right question type for the field. Dates work best as date questions, notes as long text, and the report must go to a document question or a Documents tab.
If you want the verdict in a multiple-choice question, its options have to match exactly the wording Pinpoint writes. Copy all eight:
Pass Digital
Pass Time Limited Digital
Pass Share Code
Pass Time Limited Share Code
Pass Conditional
Pass Conditional Time Limited
Rejected
Needs review
A short text question avoids this entirely, and is the safer choice if you're not sure.
Answers a person has edited by hand are never overwritten by a later check. If a check is re-run, only the answers Pinpoint filled in itself are updated.
Automating the check with stage actions
As well as onboarding, the TrustID action can be attached to a stage action, so the Right to Work check is sent automatically whenever a candidate moves into a particular stage of your hiring process - with no manual step at all. Ask your Customer Success Manager to enable this for your account.
Getting the results out of Pinpoint
Because the outcome is stored as onboarding answers as well as on the check itself, it's available to your reporting and to the Pinpoint API - so you can pull Right to Work outcomes and expiry dates into your own systems, rather than reading them off a PDF.
Troubleshooting
I can't see Send to TrustID in the Application Actions menu.
Either the integration isn't enabled for your account yet, or you don't have the "Initiate an integrated background check" permission. Ask an admin at your organisation about the role, and your Customer Success contact about the integration.
TrustID isn't in the Provider list when I add a Background Check step.
The TrustID onboarding step has to be enabled for your account by Pinpoint. Ask your Customer Success contact.
The panel says "Missing Configuration".
The TrustID credentials haven't been added yet, or one of them is missing. Send the five values from What you need from TrustID to your Customer Success contact.
Submitting fails with a login error.
Almost always because a TrustID web login was supplied instead of TrustID API credentials. Ask TrustID for API access.
The invitation was sent but the check never completes.
Either the candidate hasn't finished their TrustID journey - the invitation is emailed by TrustID, so ask them to check their inbox and spam folder - or TrustID isn't sending completion callbacks for your branch. Ask TrustID to confirm those are enabled.
The check completed but my onboarding answers are empty.
Results are only written for checks sent by an onboarding Background Check step. A check sent by hand from an application shows its results on the check itself but writes no answers. If the check did come from a step, check that the destination question is on the candidate's process, is banked, has a reporting name, and is a suitable question type.
One answer filled in but another didn't.
Usually the question type. A verdict written into a Yes/No or checkbox question is skipped rather than guessed, and a multiple-choice question only accepts an exact option match - check its options against the eight values above.
The report won't download.
TrustID keeps results for around 30 days, after which the report can no longer be retrieved. Ask your Customer Success Manager to map the report to a document destination so Pinpoint keeps its own copy of future reports.
FAQs
Q: Can I re-send a check to the same candidate?
A: Yes. Send the action again and a new invitation is created. The new check appears alongside the previous one, so you keep the full history.
Q: Does the candidate need a Pinpoint login?
A: No. TrustID emails them directly and they complete the check on TrustID.
Q: Can I use this at the same time as our older TrustID integration?
A: Yes - the two run side by side, so you can move across at your own pace.
Q: Does Pinpoint decide whether someone has the right to work?
A: No. TrustID performs the check and returns the outcome; Pinpoint records it, and flags anything needing a human look as Consider.
Related articles
Using the TrustID Integration (earlier version)