Customer setup guide · Quick start
Set up your public job board
Configure the OndaWorx Job Board and Applications for an Experience Cloud site. Follow these twelve steps to give visitors access to published jobs, accept applications and check the result while signed out.
Install the OndaWorx package and create an Experience Cloud site. The package includes an OW Job object and an OW Application object. We recommend an LWR site. Use the guest user belonging to the actual public site. If you use your own job object, update the Job Board metadata and permissions for that object.
Connect the public site
Find the site guest user
Open the guest user profile for the Experience Cloud site that will host your public board.
Allow the components to run
On that profile, open Enabled Apex Class Access and add all four classes.
- OWApplicationController
- ondaworx.OWJobDetailController
- ondaworx.OWJobListController
- ondaworx.OW_JobLocationController
Give access to configuration
In Enabled Custom Metadata Type Access, enable the types below. Packaged permission sets can supply these grants when guest assignment is available.
- 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
Enable configuration and record access
Set object permissions
Give the site guest user the following object access. Leave View All and Modify All off for both objects.
| Object | Read | Create | Edit | Delete |
|---|---|---|---|---|
| OW Job | Yes | No | No | No |
| OW Application | Yes | Yes | No | No |
Record access: In the tested packaged setup, the public Job Board can show published jobs without a separate guest sharing rule. Do not create one as a routine installation step. A guest sharing rule would grant public record-level read access to every record it matches. Keep OW Application records private, and confirm signed-out visitors cannot view existing applications or unpublished jobs.
Choose the fields visitors can use
OW Job fields
Allow Read on the job fields used by the board. This list describes the packaged OW Job object.
- Annual Salary
- Country
- County
- Created Date
- Employment Type
- Industry
- Job Description
- Job Number
- Position Title
- Published
- Short Description
- State / Region
- Work Location
OW Application fields
Assign OW Applications Standard Model Submitter. For the packaged OW Application model, it grants Read and Edit on the writable fields below. If guest permission-set assignment is unavailable, mirror these grants on the guest profile.
- Application Date
- Consent Accepted
- Consent Date
- Consent Text
- Cover Note
- Phone
- Privacy Policy URL
- Source
Why some boxes differ: First Name, Last Name, Email, Job Number and Status are defined as universally required packaged fields, so they may not appear as ordinary editable field grants. The application number is generated automatically. Do not grant extra guest access merely to make every field appear checked.
Enable applications and optional CVs
Switch on CV uploads if offered
In Salesforce Files General Settings, enable both settings below for an LWR site.
- Allow site guest users to upload files
- Use the File Upload Lightning web component for LWR sites
Assign the packaged permission sets
Where guest assignments are supported, assign all three permission sets to this site guest user. Otherwise, mirror their access on the guest profile.
- OW Job Board Runtime
- OW Applications Submitter
- OW Applications Standard Model Submitter
Example: open OW Applications Submitter → Manage Assignments, select the site guest user, and confirm the assignment succeeds.
Build the LWR pages
Create the pages and place the components
In Experience Builder, create a Jobs list page and an Object Page for OW Job to show one job. Give the detail page a route that receives the current job record ID. Put OndaWorx Job List on the Jobs page; put OndaWorx Job Detail, Job Location and Application Form on the OW Job object page. The View Job link must open that detail route.
Set the component properties
Use the packaged page configuration names shown below. Enter {!recordId} on the record detail page: it refers to the job being viewed, not to one fixed 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 |
The packaged Application Form already supplies Default as its context setting. Confirm that it is present. Leave other optional settings at their tested defaults unless your site needs a different route or behaviour.
Set privacy details and test
Set your privacy details
In the Application default context, enter your privacy policy URL and approved consent wording before accepting real submissions.
Publish and check as a visitor
Publish the LWR site. Open its public URL in a private browser window while signed out, and run the checks below.
- A published job appears and its detail link opens.
- An unpublished job stays hidden.
- A sample application creates an OW Application record visible to staff.
- If CV upload is enabled, the sample CV appears under Files on that Application and staff can open it.
- A signed-out visitor cannot browse existing Applications or CVs.
CV not showing? Check the Salesforce Files settings above, then open the new OW Application record and check its Related → Files list.
Your public site is ready for a final review
Keep a published test job and a sample application for your internal check. Confirm permissions and privacy wording with your Salesforce administrator before taking real submissions.