Job Board implementation · Step 1
Install and configure public access
Set up the public Salesforce Experience Cloud access required by the OndaWorx Job Board and Applications. The standard setup displays published jobs, opens individual job pages and lets candidates submit applications directly into Salesforce.
Before you start
OndaWorx Applications is included with the Job Board. These instructions assume candidates will apply using the OndaWorx Application Form on the Job Detail page.
Before following this guide, make sure you have:
- The approved OndaWorx managed package installed.
- Salesforce Setup access.
- An Experience Cloud site created for the public Job Board.
- Access to Experience Builder for that site.
- At least one Job record available for testing.
Using your own Job object? This is supported. Wherever this guide refers to the packaged OW Job object and fields, grant equivalent access to the customer's own Job object and the fields that will be displayed or used publicly.
The standard OndaWorx setup uses the included Application Form. A customer can instead send candidates to an external ATS, another website or a different application process, but that is an alternative configuration. The Application permissions and page setup described below would then need to be adapted.
Understand the OndaWorx permission sets
The managed package installs several OndaWorx permission sets. They are designed for different types of users.
The two Administrator permission sets are for Salesforce administrators or appropriate internal users. They are not required for candidates using the public site.
Assign the three public permission sets where Salesforce allows it
If your Salesforce org allows permission sets to be assigned to the Experience Cloud guest user, assign these three:
- OW Job Board Runtime
- OW Applications Submitter
- OW Applications Standard Model Submitter
To assign one:
If you can select the site's guest user: assign all three public permission sets above and save.
This can vary by Salesforce configuration. It is not a problem. Continue with the Guest User Profile instructions below. The following sections show you how to grant the required public access directly on the site's Guest User Profile.
Configure the Guest User Profile
Open the correct Guest User Profile
Every public Experience Cloud site has its own guest user. Make sure you are editing the profile belonging to the site that will actually host the Job Board.
Enable the OndaWorx Apex classes
On the Guest User Profile, find Enabled Apex Class Access, click Edit and add the following classes.
- OWApplicationController
- ondaworx.OWJobDetailController
- ondaworx.OWJobListController
- ondaworx.OW_JobLocationController
Do not worry about the namespace. Salesforce may show ondaworx. before packaged class names. This is normal.
Enable the OndaWorx Custom Metadata Types
Still on the Guest User Profile, open Enabled Custom Metadata Type Access and enable the types below.
You do not need to understand or configure these records yet. You are simply allowing the public OndaWorx components to read their configuration.
- OW Application Context
- OW Application Field Mapping
- OW Application Target
- OW Job Board Detail Field
- OW Job Board Field
- OW Job Board Filter
- OW Job Board Page
- OW Job Board Route Dimension
- OW Job Board Search Filter
- OW Job Board Sort
- OW Job Detail SEO
- OW Job Location
- OW Job SEO Employment Map
The Members screen controls users who log in to the site. Public Job Board visitors are not logged in. The public access described here belongs to the site's Guest User Profile.
Allow visitors to read published jobs
Give Read access to the Job object
On the Guest User Profile, open the object settings for OW Job.
| Object | Read | Create | Edit | Delete |
|---|---|---|---|---|
| OW Job | Yes | No | No | No |
Leave View All and Modify All switched off.
Give Read access to the Job fields used publicly
Give the Guest User Profile Read access to the fields used by the public Job Board.
- Annual Salary
- Country
- County
- Created Date
- Employment Type
- Industry
- Job Description
- Job Number
- Position Title
- Published
- Short Description
- State / Region
- Work Location
Adding another field later? If you configure the Job Board to display or use another Salesforce field, remember to give the Guest User Profile Read access to that field as well.
In the tested packaged setup, the public Job Board can display eligible published jobs without creating a broad guest sharing rule as a routine installation step. Do not create one unless the customer's Salesforce sharing model specifically requires it. Always confirm the result while signed out.
Allow visitors to submit applications
OndaWorx Applications is part of the normal Job Board setup. A visitor needs enough access to create a new application, but must not be able to browse, edit or delete existing applications.
Set OW Application object permissions
| Object | Read | Create | Edit | Delete |
|---|---|---|---|---|
| OW Application | Yes | Yes | No | No |
Leave View All and Modify All switched off.
Allow the Application Form to use its fields
For the standard OW Application model, provide the same Read/Edit field access used by the packaged OW Applications Standard Model Submitter permission set.
- Application Date
- Consent Accepted
- Consent Date
- Consent Text
- Cover Note
- Phone
- Privacy Policy URL
- Source
Some required fields may look different. First Name, Last Name, Email, Job Number and Status are packaged required fields and may not appear as ordinary editable field permissions. The Application Number is created automatically.
A visitor should be able to submit a new application, but must never be able to browse or open another candidate's Application. You will test this while signed out at the end of this guide.
Enable CV uploads if required
Applications are part of the standard Job Board. Uploading a CV is optional. If the customer wants candidates to attach a CV, enable the Salesforce file settings below.
Enable guest file uploads
- Allow site guest users to upload files
- Use the File Upload Lightning web component for LWR sites
No CV upload? Leave these settings unchanged and continue with the rest of the setup.
Create the Experience Cloud pages
Create the Jobs page and Job Detail page
In Experience Builder create:
- A Jobs page containing the OndaWorx Job List.
- An Object Page for OW Job used to display an individual Job.
On the OW Job object page add:
- OndaWorx Job Detail
- OndaWorx Job Location
- OndaWorx Application Form
The Detail page route must receive the current Job record ID so each View Job link opens the correct Job.
Set the component properties
Select each component in Experience Builder and enter the standard settings below.
{!recordId} means “the Job currently being viewed”. Do not replace it with one example Job ID.
| Component | Experience Builder property | Value |
|---|---|---|
| Job List | Job Board Page Developer Name | Jobs |
| Job Detail | Record Id | {!recordId} |
| Job Detail | Job Board Page Developer Name | Job_Detail |
| Job Location | Job Record ID | {!recordId} |
| Job Location | Job Board Page Developer Name | Job_Detail |
| Application Form | Record Id | {!recordId} |
| Application Form | Application Context Configuration | Default |
Leave other optional component properties at their standard values unless the customer's implementation specifically requires different behaviour.
Add the customer's privacy details
Update the Default Application Context
Before accepting real applications, open the Default Application Context and enter the customer's approved:
- Privacy Policy URL
- Consent wording shown to applicants
Do not leave example or placeholder privacy wording in a live site.
Publish and test while signed out
Test as a real public visitor
Publish the Experience Cloud site. Then open the public URL in a private/incognito browser while completely signed out of Salesforce.
- A published Job appears in the Jobs list.
- The View Job link opens the correct Job Detail page.
- An unpublished Job stays hidden.
- The Job Location information displays correctly.
- The Application Form appears against the correct Job.
- A sample application creates an OW Application record visible to staff.
- The new Application is linked to the correct Job.
- The privacy wording and Privacy Policy link are correct.
- If CV upload is enabled, the uploaded CV appears under Files on the new Application.
- A signed-out visitor cannot browse or open existing Applications or CVs.
CV not showing? Recheck the Salesforce Files settings in section 06, then open the new OW Application and check Related → Files.
Before changing the Job Board configuration, check that all OndaWorx Custom Metadata fields are visible. Continue to Prepare Custom Metadata layouts .
Next: prepare the configuration screens
The Custom Metadata layout check is normally a one-time post-installation task. After that, the remaining guides take you through Job Board pages, fields, filters, Job Detail, SEO, URLs and final testing.