Send candidate email and calendar invites from your Gmail.
Why it exists Candidates receive mail from you, not a system address.
Email from a system address is a worse experience for everyone: it is more likely to be filtered as automated mail, it discourages candidates from replying, and when they do reply the answer goes somewhere nobody is watching. Sending through your own mailbox fixes all three — the message comes from a named human at a real company, replies come back to you naturally, and deliverability is dramatically better because it is ordinary business mail. The same connection powers calendar sync and Google Meet link generation.
How to use it
Go to Settings and click the "Google" card under Integrations.
Click the connect action to start hosted sign-in via Unipile.
Complete Google's sign-in and consent screens.
Return to Canvider and confirm the connection shows as ready.
Requires employer tier 2 or higher; disconnect Microsoft first if it is connected.
Use "Send test" to verify email delivery.
Good to know
Requires employer tier 2 or higher.
Google and Microsoft are mutually exclusive — only one email integration can be connected at a time.
Connecting also unlocks calendar sync and one-click Google Meet links, not just email.
Run "Send test" immediately after connecting; discovering a delivery problem via a silent candidate is much worse.
Sign-in is hosted via Unipile, so Canvider never handles your Google password.
Send candidate email and calendar invites from Outlook or Office 365.
Why it exists Aligns candidate correspondence with your Microsoft workplace.
For companies standardised on Microsoft 365, this is the equivalent of the Google integration and exists for the same reasons: candidate mail that comes from a real person, replies that land in the mailbox you actually read, and calendar entries in the system your colleagues check. The Teams link generation is often the deciding factor in practice, since interviewers who live in Teams should not have to join a different platform for interviews.
How to use it
Go to Settings and click the "Microsoft" card under Integrations.
Click the connect action to start hosted sign-in via Unipile.
Complete the Microsoft sign-in and consent screens.
Return to Canvider and confirm the connection is ready.
Requires employer tier 2 or higher; disconnect Google first if it is connected.
Teams meeting links now become available when scheduling interviews.
Good to know
Requires employer tier 2 or higher.
Only one of Google or Microsoft can be connected at a time; disconnect the other first.
Some Microsoft 365 tenants restrict third-party app consent — if sign-in fails, your IT administrator may need to approve it.
Once connected, Teams links can be generated directly in the Schedule Interview modal.
Use the diagnostics tools to send a test email and create a test meeting before relying on it.
Connect LinkedIn for job posting, sourcing and profile enrichment.
Why it exists Unlocks automated posting and richer candidate context.
LinkedIn is the largest professional dataset in the world and the primary channel for most white-collar hiring, so connecting it unlocks three capabilities at once rather than one: automatic job posting, LinkedIn candidate sourcing, and profile enrichment on your applicants. The important architectural detail is that all of this runs through your own LinkedIn account and its ordinary permissions — Canvider is not a back door to data you could not otherwise see, and your account's limits and LinkedIn's terms apply exactly as they normally do.
How to use it
Go to Settings and click the "LinkedIn" card under Integrations.
Click the connect action to start hosted sign-in via Unipile.
Complete LinkedIn's sign-in and any verification steps.
Return to Canvider and confirm the account shows as connected.
Requires employer tier 2 or higher.
LinkedIn sourcing, automatic job posting and profile enrichment are now available.
Good to know
Requires employer tier 2 or higher.
Everything runs through your own LinkedIn account, so your account's limits and LinkedIn's terms of use apply.
Unlike email, LinkedIn is independent — it does not conflict with a Google or Microsoft connection.
LinkedIn occasionally requires re-verification, which shows up as "Action needed" in the connection panel.
Manual guided job posting remains available and requires no connection at all.
Shows which LinkedIn company pages you can publish jobs as.
Why it exists Confirms the job will post under the right company identity.
A job posted under the wrong LinkedIn identity is a genuine problem, not a cosmetic one — candidates check the posting company, and a role advertised by a dormant page or the wrong regional entity looks like a scam. Groups with several legal entities, brands or country pages hit this regularly. This panel makes the identity explicit before you publish rather than after, and it is the first place to look when a posted job appears under a name you did not expect.
How to use it
Go to Settings → LinkedIn after connecting your account.
Scroll to "Company pages for LinkedIn posting".
Review the list of pages you administer.
When LinkedIn is selected during publish, Canvider posts to one of these pages.
If the expected page is missing, verify your LinkedIn admin rights and reconnect.
Good to know
Only pages where your LinkedIn account has admin rights appear here — a missing page is almost always a permissions issue on LinkedIn's side.
Fix admin rights on LinkedIn first, then reconnect; reconnecting alone will not grant access you do not have.
Check this before your first automated post, especially if your group has multiple entities or country pages.
The page that appears here is the identity candidates will see on the posting.
Live status panel for each connected Google, Microsoft or LinkedIn account.
Why it exists Tells you immediately when a connection has expired.
Integrations do not fail loudly. A session expires because a password changed or a platform required re-verification, and the symptom is silence — emails that do not arrive, a calendar that stops syncing, sourcing that returns nothing. Because the failure looks like ordinary quiet, it can go unnoticed for days while candidates wait. This panel makes the state explicit, and its four values map to four different actions, which is why it is worth reading rather than glancing at.
How to use it
Go to Settings and open the Google, Microsoft or LinkedIn card.
Read the "Connection" panel state: Connected, Action needed, Finishing setup, or Not connected.
If it says "Connected", check the signed-in address shown.
If it says "Action needed", click the Reconnect button to restore the session.
If it says "Finishing setup", click "Refresh status" after completing sign-in.
On the LinkedIn page, review "Connected profile" and click "View on LinkedIn" to verify the identity.
Good to know
"Action needed" means the session expired and the feature has already stopped working — reconnect immediately.
"Finishing setup" usually just needs "Refresh status" after you completed sign-in in the other tab.
Verify the signed-in address, not just the green state; connecting the wrong account is an easy mistake to miss.
Check this first whenever email, calendar sync or sourcing mysteriously stops working.
Internal tools to test email, calendar and LinkedIn API access.
Why it exists Confirms an integration actually works before relying on it.
A connection showing green means authentication succeeded, which is not the same as the feature working — permissions can be partial, a tenant policy can block calendar writes, and LinkedIn scopes can be narrower than expected. The gap between "connected" and "actually functional" is normally discovered when a candidate says they never got the invitation. These tools close it by exercising the real operations on demand, which turns a vague "is this working?" into a definite answer in under a minute.
How to use it
Go to Settings and open the Google, Microsoft or LinkedIn integration page.
Scroll to the "Internal tools" section.
On Google/Microsoft, click "Send test email" to send a short message from the connected account.
Click "Schedule test meeting", enter an "Attendee email", and submit to create a 30-minute test event.
On LinkedIn, use "Profile lookup (debug)" with a profile URL or username, then click "Fetch profile".
Use the "API capability checks" buttons (Own profile, Job postings, Recent chats) to verify scopes.
These tools are for verification only — they are hidden when internal tools are disabled.
Good to know
Use your own address as the test attendee — the test meeting creates a real calendar event.
Run these right after connecting and again whenever something stops working; it isolates the problem in a minute.
The LinkedIn capability checks tell you which scopes were actually granted, which explains most "why doesn't sourcing work" questions.
The section is hidden when internal tools are disabled, so its absence is not a fault.
Remove a connected Google, Microsoft or LinkedIn account.
Why it exists Revokes access or frees the slot for another account.
There are three ordinary reasons to disconnect: the person whose account was connected is leaving, you are switching from Google to Microsoft (or vice versa, since only one can be connected), or you want to revoke access as a precaution. The consequence is immediate and broad — candidate email falls back to the Canvider address, calendar sync stops, and on LinkedIn both sourcing and enrichment stop working. Plan the reconnection before disconnecting, especially if interviews are already scheduled.
How to use it
Go to Settings and open the relevant integration card.
Find the connected account details on that page.
Click the disconnect action.
Confirm the disconnection.
Features depending on that account stop working until you reconnect.
Good to know
Disconnect the outgoing account before someone leaves the company, not after their credentials are revoked.
Switching between Google and Microsoft requires disconnecting the current one first.
Existing synced calendar events remain in the external calendar, but future changes stop propagating.
Sent email history stays in Canvider; only the ability to send from that mailbox goes away.
Turns PostJobFree application emails into applications automatically.
Why it exists Captures applications from PostJobFree without manual entry.
Many job boards, PostJobFree among them, deliver applications as plain email with the CV attached rather than through an API. Those candidates would otherwise live in a mailbox — unscored, unsearchable and absent from your reporting — and typically get slower responses than everyone else. This ingestion parses the message, extracts the attached resume (with OCR when the PDF is a scan), and runs the same AI extraction as any other application, so a board that offers no integration still produces first-class records in your pipeline.
How to use it
Publish your job to PostJobFree from the "Publish Job" step.
Wait for applications to arrive as email in the configured mailbox.
Open the People page.
Click "Refresh Applicants".
Canvider parses each email, extracts the PDF resume (with OCR fallback), and runs AI extraction.
Review the newly created applications in the list.
Good to know
Nothing arrives until you click "Refresh Applicants" — make it a daily habit if you use this channel.
OCR handles scanned CVs but is slower and less accurate than a text PDF, so check extracted facts on those.
Candidates ingested this way have no screening-question answers, since they applied through the board's form.
Applications are attributed to PostJobFree, which is what makes the source-effectiveness comparison meaningful.
Lets AI assistants query your Canvider data securely.
Why it exists Brings ATS answers into Cursor, Claude Desktop and similar tools.
Recruiting questions arrive in the middle of other work — during a planning conversation, while writing a board update — and the cost of switching tools to answer them is why so many go unanswered. MCP lets an AI assistant you already have open query Canvider directly, so "how many open vacancies do we have?" is answered in the conversation you are already in. The security model is the important part: each key is scoped to a single employer and can be revoked or expired, so the assistant can never reach beyond your own company's data.
How to use it
Request a Canvider API key for your company — your administrator can obtain one from Canvider support.
Open your MCP config file (e.g. ~/.cursor/mcp.json).
Add a canvider server entry pointing at https://ats.canvider.com/api/mcp/.
Set CANVIDER_API_KEY to your key and CANVIDER_API_URL to the endpoint.
Restart Cursor or Claude Desktop.
Ask your assistant questions like "How many open vacancies does my company have?".
Each key is scoped to one employer and can be revoked or expired.
Good to know
Keys are issued per company on request; they are not self-served from the settings interface.
Each key is scoped to one employer and can be revoked or given an expiry — issue individual keys rather than sharing one.
Treat the key like a password: it grants access to candidate data, and it belongs in a config file, not in a chat message or a repository.
API requests are rate limited to 100 per hour.
Restart your assistant after editing the config, or the server will not be picked up.