This is a build-to-order module, not an instant apps.odoo.com download. Typical lead time is one working week from kickoff, depending on how many boards you need and how each board's API access is set up on your accounts. You get a UAT build to review first, then we deploy to production. If you only need two boards on a clean Odoo.sh instance it can land toward the shorter end; adding region-specific boards like Bayt or Naukri that require employer-account onboarding pushes it later.

Every engagement includes a defined post-go-live support window covering bug fixes and, critically, break-fixes when a job board changes or deprecates its API — the main reason generic marketplace connectors rot. During the window we keep the connectors working, respond within the agreed SLA, and assist with the Odoo point releases you run. Extended support and adding new boards later are available as a follow-on; we scope those before your window ends so there is no gap.

Out of the seed set we cover LinkedIn, Indeed, Bayt and Naukri, and we regularly add others (Monster, Glassdoor, GulfTalent, regional and niche boards) depending on where you hire. Each connector depends on that board offering an API, indexing feed, or official partner program and on you holding the appropriate employer account — we confirm feasibility per board during scoping before committing to it.

Yes. We build and version-pin the addon to Odoo 17, 18 or 19, and it works on both Community and Enterprise since it builds on the standard Recruitment app (hr.job, hr.applicant) and core UTM models. If you later upgrade Odoo, keeping the module compatible with the new major version is handled as an upgrade engagement.

Applicants return two ways: a scheduled ir.cron job polls each board's API for new applications, and each vacancy also gets an inbound email alias that captures applications forwarded by boards that email you. Both paths create hr.applicant records in the correct job and stage with the CV attached. We de-duplicate by candidate email, so someone who applies on two boards becomes a single record, and every applicant is stamped with the source board via source_id / medium_id / campaign_id.

Yes. Board API keys and tokens live on dedicated models protected by ir.model.access.csv and record rules, so only authorized configuration users can see or edit them — standard recruiters never touch raw credentials. For agencies, record rules isolate each client's boards and applicants. All outbound calls go over authenticated, encrypted connections, and failed calls are logged with the board's response rather than exposing secrets in tracebacks.

Yes. You can override the title, description, salary display and category mapping for a specific board without changing the master vacancy, which matters for bilingual MENA postings or region-specific formatting. On the reporting side, because we reuse Odoo's native utm.source/medium/campaign, source attribution flows straight into the built-in Recruitment analytics; we can also deliver a QWeb per-campaign summary or a cost-per-hire-by-board dashboard as a scoped add-on.