Verify talent and company profile items
Check the licences, cards, certificates, jobs and schools on talent and company profiles, show a Verified badge, and keep it only while the checked details stay the same.
A
JVerification lets your team confirm the details on a talent or company profile and show a Verified badge on each confirmed item. You choose which fields a check covers. The badge stays while those fields stay the same, so a changed card number or a new employer always goes back to your team.
Each item is verified on its own:
- Collection fields: every row of Repeatable details is one item. A field with no repeatable details is verified per selected entry. This works for any collection reference field on talent or company profiles, such as licences, trade cards, certificates or memberships.
- Experience: each job on a talent profile, checked on its company name and company website.
- Education: each school on a talent profile, checked on its school name and school website. The badge confirms the school, not that a degree was awarded.
Verification is included on every paid plan, starting with Starter. Job seekers and company members request it on boards built with the AI website builder or the Board SDK, and your team decides in the dashboard or through the API.
Switch on experience and education
- Open Settings → Talent profile.
- Click the Experience or Education field.
- Turn on Verification and save.
Both have a fixed setup. An experience item is checked by a work email at the company website's domain, for a current job only; a past job goes to your team. An education item is checked by a school email at the institution website's domain. A subdomain counts, so student.ox.ac.uk passes for ox.ac.uk, and personal email providers are refused. Your team can always verify either kind by hand. Changing the company or school name or website moves the item to Changed. These items never expire.
Set up a collection field
- Open Settings → Talent profile or Settings → Company profile.
- Edit the collection reference field, or add one. See Connect a collection to profiles.
- In the Verification section, turn on Verify items.
- Set the options below, then click Save field.
| Setting | What it does |
|---|---|
| Checked fields | The detail fields the check covers. Changing any of them, or changing the selected collection entry, moves a verified item to Changed |
| Expiry | Never, On one of the item's date fields, or Every N months (1 to 120) |
| Verified by | Your team reviews each request. Email domain lets the job seeker confirm an address at a domain taken from one of the item's URL or short text fields, or from A list of domains you enter (up to 50) |
| Required | Marks the item as one employers should see verified. The setting comes with the field definition, so your site can show Not verified to employers on an unverified required item. Nothing is blocked |
The date field an item expires on is always part of the check, so editing the date never extends a badge. The same applies to the field an email domain comes from. Email domain checks are for talent profiles; company items always go to your team.
How expiry works
With On a date field, the verification holds through that day (UTC). With Every N months, it lapses that many calendar months after it was verified. Either way, the job seeker gets a reminder email 30 days before, and a second email when the item lapses. A lapsed item shows Expired in your dashboard, and the job seeker can ask for a new check.
Statuses
| Status in the dashboard | API value | Meaning |
|---|---|---|
| Not requested | unverified | Nobody has asked yet |
| Pending | pending | Waiting for your team. Edits while pending keep it pending |
| More information needed | needs_info | Your team asked the job seeker for more |
| Verified | verified | Checked and confirmed |
| Rejected | rejected | Checked and wrong. It stays rejected until a checked field is edited |
| Unable to verify | unable_to_verify | Could not be checked, through no fault of the job seeker |
| Changed | changed | A checked field was edited after the item was verified or rejected |
| Expired | lapsed | Past its expiry date or re-check date |
| Verification removed | revoked | Your team took the badge away |
The job seeker gets a branded email when an item is verified, rejected, sent back for more information or has its verification removed.
Who sees what
- Everyone, signed in or not: a Verified badge on verified items, with the confirmed email domain when it was verified by email. Other statuses are not shown.
- Employers: the same badge, plus Not verified on unverified items whose field is Required, where your site shows it.
- The job seeker or company member: every status on their own items, with the reason for the last decision.
- Your team and API keys: everything, including the staff note.
Verification follows the field's visibility. A private field's items appear only to the profile owner and your team.
Review requests
- Open Job seekers or Companies in your dashboard.
- Set the Verification filter to Needs verification. The list shows every item waiting for a decision.
- Click Review on an item. The dialog shows the item's Checked details and its Current status.
- Choose a Decision: Verify, Reject, Ask for more information, Mark as unable to verify or Remove verification. Every decision except Verify needs a Reason. Add a Staff note if you like; job seekers never see it.
- Click Save decision.
You can also decide on an item nobody has asked about yet, for example when your team checks cards proactively. Click Review on any item in the profile's verification list.
Each status allows these decisions:
- Verify: any status except Verified.
- Remove verification: Verified.
- Reject and Mark as unable to verify: Not requested, Pending, More information needed, Changed and Expired.
- Ask for more information: the same, except More information needed.
If the job seeker edited a checked field while the dialog was open, Cavuno refuses the decision and asks you to look again, so you only ever verify the details you saw. Team members who can manage job seekers or companies make decisions.
Privacy
Cavuno stores a fingerprint (a one-way hash) of the checked values at the time of each decision, never a copy of them. A later edit is compared against that fingerprint. For email checks, only the domain and the date are kept, never the address.
Existing values are not imported. When you switch verification on, every item starts unverified.
Example: construction cards
A trades board wants employers to trust the site cards job seekers list.
- Create a Construction cards collection with one entry per card scheme. See Create a collection.
- In Settings → Talent profile, add a collection reference field labelled
Construction cards, keyconstruction_cards, using that collection, with Multiple selections. - Add Repeatable details:
card_number(Short text, Show on public profile off),card_type(Short text),colour(Short text),occupation(Short text) andexpiry_date(Date). - In Verification, turn on Verify items, tick all five Checked fields, set Expiry to On Expiry date, Verified by to Your team, and turn on Required.
Each card a job seeker adds is one item. Your team checks it against the scheme's register and verifies it. The badge shows on the public profile without the private card number. If the job seeker changes the card number, type, colour, occupation or expiry date, the card moves to Changed until your team checks it again. The job seeker is reminded 30 days before the card expires, and the badge lapses after that day.
Ask the AI builder
Show profile item verification on the talent profile and the job seeker's account. Use the starter's built-in verification UI for experience, education and collection items, and never build your own verification status field. For the
construction_cardsfield, render one row per entry with its card type, colour, occupation and expiry date, and show the Verified badge from each entry'sverificationwhen present. For signed-in employers, show "Not verified" on an entry without a badge, because the field's verification is required. In the account page, let job seekers request verification from each card with the existing verification dialog.
Use the API
Every step works through the operator API, so Companion, your own AI agent or the MCP server can set verification up and record decisions. Recording a decision and changing collection field definitions default to Ask first in Companion, and you can set them to Always allow.
| Task | Endpoint |
|---|---|
| Set up a collection field | PUT /v1/settings/profile-object-references/{entity} with verification on the definition |
| Switch on experience or education | PATCH /v1/settings with experienceVerificationEnabled or educationVerificationEnabled |
| List a profile's items | GET /v1/candidates/{id}/verifications, GET /v1/companies/{id}/verifications |
| Read one item | GET /v1/candidates/{id}/verifications/{itemKey} (and the company equivalent), which returns currentHash |
| Decide | POST /v1/candidates/{id}/verifications/{itemKey}/decisions (and the company equivalent) |
| List the queue | GET /v1/candidates/verifications, GET /v1/companies/verifications, filtered by status (default pending) |
An itemKey is experience:{id}, education:{id}, ref:{fieldKey}:{recordId} or ref:{fieldKey}:{recordId}:{entryKey}, URL-encoded in the path. A verify decision needs expectedHash, the currentHash you read; it is refused with 409 item_verification_changed if the item changed since. Every other decision needs a reasonCode: details_mismatch, not_found_in_register, document_unreadable, document_expired, suspected_fraud, issuer_unreachable or other.
Board API for the signed-in job seeker
| SDK method | Endpoint |
|---|---|
board.me.profile.listVerifications() | GET /me/profile/verifications |
board.me.profile.submitVerification({ itemKey }) | POST /me/profile/verifications |
board.me.profile.submitEmailDomainVerification({ itemKey, email }) | POST /me/profile/verifications/email-domain |
board.me.profile.confirmEmailDomainVerification({ itemKey, code }) | POST /me/profile/verifications/email-domain/confirm |
board.auth.verifyItemEmail({ token }) | POST /auth/verify-item-email |
board.me.companies.listVerifications(slug) | GET /me/companies/{slug}/verifications |
board.me.companies.submitVerification(slug, { itemKey }) | POST /me/companies/{slug}/verifications |
Each listed item has a nextStep: email when an email check is available, team when only a team review is, and none when there is nothing to do. A collection item is sent for verification once every checked field has a value; until then a request or email check returns 422 item_verification_details_missing, with details.missingFieldKeys and details.missingFieldLabels naming the fields to fill in. An email check sends a 6-digit code and a link that works for 24 hours, even signed out. An item can start 5 email checks a day and a job seeker 20. Public profile reads carry a verification badge on each verified experience, education, selection or entry.
Webhooks
candidate.verification.updated and company.verification.updated fire on every status change. The payload carries the item key, its old and new status, the reason code and where the change came from, never the item's values, the staff note or the proof file. See Webhook events.