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

Start here: Implement the Job Board

Follow these guides to configure a public OndaWorx Job Board in a customer’s Salesforce Experience Cloud site, from access and page configuration through to public testing and handover.

Begin with installation and guest permissions →

Who this is for

Salesforce administrators and implementation partners who can configure Custom Metadata, object and field access, and Experience Builder. The customer must provide the publication rules and approve which job data may be shown publicly.

Gather these before you begin

Salesforce access

Installed OndaWorx Job Board package, the installed package version, Salesforce Setup access and access to the customer’s Experience Cloud site.

Customer job schema

Job object API name and field API names for title, description, publication status, location, pay, dates and desired search controls.

Publication rule

A customer-approved definition of a public job, including how closed and expired jobs are withdrawn.

Test records

At least one published job, one unpublished job, one closed or expired job, and examples for each planned landing page.

Follow the implementation guides in order

  1. 1
    Install and configure public access

    Install the approved package and grant the public site only the access it needs. Use the existing OndaWorx installation and guest-permissions instructions.

  2. 2
    Set up pages, list fields and filters

    Create OW Job Board Page, Field, Filter and Search Filter records; build the first working job list and any static landing pages.

  3. 3
    Configure Job Detail

    Create the detail Page and its own publication filters, choose visible fields and connect the public record route.

  4. 4
    Configure Job Detail SEO

    Map customer fields to page metadata and JobPosting data, and check the canonical URL strategy.

  5. 5
    Plan landing-page URLs

    Set up tested static URLs for important categories and locations. Check the installed release before using dynamic routes.

  6. 6
    Test and hand over

    Check the published site while signed out, document the configuration and demonstrate how the customer publishes and withdraws jobs.

Scope: These guides cover the OndaWorx Job Board. The Applications module is optional and has separate submission, privacy and guest-permissions requirements. Do not use a Job Board permission checklist as the complete Applications setup.

What “ready to launch” means

  • A signed-out visitor can find and open an eligible published job.
  • Unpublished and expired jobs are excluded from search and do not expose public job content by direct URL.
  • Filters, detail links, mobile layout, browser titles, canonical URLs and structured data have been checked on the public site.
  • The customer has approved the publication rules and received the page and metadata configuration register.
Check the installed release: Start with the standard picklist filters and static landing pages described in these guides. Verify any advanced search controls or route options in the customer’s public site before including them in the launch.
Guide updated 29 September 2026. The implementation partner should record the installed package version and validate these steps in the customer’s environment.