Start here: Implement the OndaWorx Job Board
OndaWorx · Implementation documentation

Start here: Implement the OndaWorx Job Board

Follow these guides in order to configure a complete public OndaWorx Job Board in Salesforce Experience Cloud — from installation and permissions through to Jobs, Applications, SEO, URLs, testing and customer handover.

Begin with installation and public access →
The standard OndaWorx implementation includes Job Board + Applications. Candidates browse published Jobs, open a Job Detail page and apply using the OndaWorx Application Form. CV upload can be enabled if the customer wants candidates to attach a CV.

Who these guides are for

These guides are written for Salesforce administrators and OndaWorx implementation partners.

You do not need to be a Salesforce developer and you do not need to understand how the OndaWorx Apex or Lightning Web Components were built.

You should be comfortable with normal Salesforce administration tasks such as:

  • opening Salesforce Setup
  • managing object and field permissions
  • editing Custom Metadata records
  • using Experience Builder
  • testing a public Experience Cloud site
Using an external ATS or application form? The standard documentation assumes the customer uses the included OndaWorx Application Form. A customer can instead use an existing ATS, external application form or another application process, but that is an alternative configuration and may require additional setup.

What OndaWorx installs

Job Board

Public Job List and Job Detail components with metadata-driven fields, filters, sorting and pages.

Applications

Public Application Form and the standard OW Application model for receiving applications directly into Salesforce.

Job Location

Configurable location display with optional map-search functionality.

Job Detail SEO

Metadata-driven SEO titles, descriptions, canonical support and JobPosting structured data.

Configuration records

Custom Metadata Types and starting configuration records that can be adapted to the customer's Salesforce Job object and website.

Permission sets

Runtime, submitter and administrator permission sets to support the Job Board and Applications.

What the customer or implementation partner configures

Job object Which Salesforce object contains the customer's Jobs.
Public fields Which Job fields are shown to visitors.
Publication rule What makes a Job public, for example Published = true or Status = Open.
Search filters Which fields candidates use to narrow the Job List.
Experience Cloud The public Jobs page, Job Detail page and any important landing pages.
Applications Privacy wording, consent details and optional CV upload.
SEO Customer Job field mappings, hiring organisation and canonical strategy.

Gather these before you begin

Salesforce access

Installed OndaWorx managed package, Salesforce Setup access and access to the customer's Experience Cloud site.

Customer Job object

The Job object API name and the fields containing title, description, location, salary, employment type and other public information.

Publication rule

The exact Salesforce field and stored value that identify a Job as publicly available.

Application details

Customer privacy-policy URL and approved consent wording.

Website URLs

Intended main Jobs URL, Job Detail route and any important category or location landing pages.

Test Jobs

At least one public Job and one unavailable Job, plus examples covering the main filters and landing pages.

Follow these guides in order

  1. 1
    Install and configure public access Standard

    Configure the Experience Cloud Guest User, OndaWorx permission sets, Job access, Application permissions and optional CV uploads. Then place the standard components in Experience Builder.

  2. 2
    Check the Custom Metadata layouts One-time check

    Check that the OndaWorx configuration fields are visible. If everything is already visible, make no changes and continue.

  3. 3
    Set up pages, list fields and filters Standard

    Start with the supplied Jobs configuration, set the publication rule, choose the Job card fields, configure candidate search filters and set sorting.

  4. 4
    Configure Job Detail Standard

    Review the supplied Job_Detail configuration, add its publication rule, check the Detail Fields, configure Job Location and connect the Application Form.

  5. 5
    Configure Job Detail SEO Standard

    Review the supplied SEO configuration, map customer Job fields, check employment types, configure canonical behaviour where needed and validate JobPosting structured data.

  6. 6
    Configure URLs and landing pages Standard

    Connect OndaWorx Page records to real Experience Cloud URLs and create useful static Job landing pages. Dynamic Route Dimensions are covered separately as an advanced option.

  7. 7
    Test and hand over Final check

    Test Jobs, Job Detail, Applications, security, SEO and URLs while signed out. Record the customer's configuration and demonstrate normal Job publishing and application management.

Standard implementation ends here. If the seven steps above have passed their public tests, the core OndaWorx Job Board and Applications implementation is complete.

Free companion utility: OndaWorx Job SEO Links

Supplied free, but installed separately. OndaWorx Job SEO Links is provided free to OndaWorx Job Board customers but is not included inside the main managed Job Board package. OndaWorx supplies the separate companion package when the customer receives the Job Board package.

Job SEO Links adds useful crawlable internal links to individual Job pages, for example:

Permanent IT Jobs in Yorkshire · Permanent IT Jobs · IT Jobs

This can help visitors navigate to related Jobs and improves the internal linking structure of the public Job Board.

Install it after the main Job Board is working.

Configure OndaWorx Job SEO Links →

Job Detail SEO and Job SEO Links are different. Job Detail SEO is part of the managed Job Board and controls SEO metadata and JobPosting structured data. Job SEO Links is the separately supplied free companion utility that creates internal links.

Standard setup versus advanced options

Feature Standard implementation?
Public Job List Yes
Job Detail Yes
OndaWorx Applications Yes
Job Location Yes
Job Detail SEO / JobPosting Yes
Static Job landing pages Yes, where useful
CV upload Optional
Job SEO Links Free companion utility supplied separately
External ATS / external application process Alternative configuration
Dynamic Route Dimensions Advanced
Google Indexing API Not required for standard OndaWorx setup

What “ready to launch” means

  • a signed-out visitor can open the public Jobs page
  • only eligible published Jobs appear
  • unavailable Jobs are not exposed as active vacancies by direct URL
  • Job cards, filters and sorting work correctly
  • Job Detail displays the correct Job information
  • Job Location behaves correctly
  • candidates can submit an Application successfully
  • Applications and uploaded CVs remain private
  • privacy wording and the customer's Privacy Policy link are correct
  • SEO title, description, canonical and JobPosting have been checked
  • important public URLs work directly and after refresh
  • the site works on a mobile-sized screen
  • an authorised customer user can publish and withdraw Jobs normally
  • the customer has received a record of its configuration
Always complete the final checks while signed out. Being logged into Salesforce as an administrator can hide Guest User permission problems. The public Job Board must be tested as an ordinary website visitor.

Quick glossary

Developer Name
Salesforce's permanent internal name for a configuration record. For example, the standard OndaWorx Jobs Page uses: Jobs and the standard Job Detail Page uses: Job_Detail.
API Name
Salesforce's technical name for an object or field. For example: OW_Job__c or County__c. OndaWorx uses API Names to know which Salesforce data to read.
Custom Metadata
Salesforce configuration records used by OndaWorx. Editing Custom Metadata changes how the package behaves without changing the package code.
Route
The public website path used to open a page. For example: /jobs or /job-detail.
Canonical URL
The URL search engines should treat as the preferred version of a page when the same content could appear at more than one URL.
JobPosting structured data
Machine-readable Job information added to a Job Detail page so search engines can understand information such as title, location, salary, employment type and dates.
Guest User
The Salesforce user identity used by someone visiting a public Experience Cloud site without logging in. Public OndaWorx permissions must be tested using this signed-out experience.
Ready to begin? Start with: Install and configure public access →
Guide updated 10 October 2026. These guides describe the standard OndaWorx Job Board and Applications implementation. Record customer-specific differences as part of the final handover.