Procedure
Create a career site
Create a career site and set its context so the right requisitions appear to the right external candidates, and nothing else does.
When to use
Use this procedure when creating a new external career site, whether it serves one audience or several differentiated by location, organization, job category, job function or recruiting type. Do not use it to change an existing site's context in place; a wrong context on a live site publishes or hides jobs immediately, so verify against a draft or a narrower site first.
Access assumptions
A procedure followed by the wrong person is a security incident, so these are stated explicitly rather than assumed.
- Ability to run the Career Sites Configuration task under the Candidate Experience functional area
- Read access to job requisitions and their location, organization, category, function and recruiting type attributes
- Read access to the requisition flexfields used as context
Prerequisites
- The Recruiting and Candidate Experience offering has been opted in to
- Job requisitions exist in a state that permits posting
- A decision has been made about which requisitions this site should show
Pre-checks
Do these before starting. Each one prevents a failure that is expensive to undo once configuration exists.
- 1.Write down the intended rule in plain language before configuring it. "UK roles only" and "UK roles in UK Operations" are different contexts and produce different sites.
- 2.Confirm the organizational hierarchy, because a parent context publishes its children.
- 3.Confirm whether the site is intended to be public to all external candidates. A wrong context on a public site is a disclosure risk, not just a usability one.
Steps
Open Career Sites Configuration
In the Setup and Maintenance work area, go to Offering: Recruiting and Candidate Experience, Functional Area: Candidate Experience, Task: Career Sites Configuration.
Expected outcome: The Career Site Look and Feel Configuration page is open.
Path:
Setup and Maintenance > Offering: Recruiting and Candidate Experience > Functional Area: Candidate Experience > Task: Career Sites ConfigurationStart a new site
Click the Add Site icon, then enter a name and a code for the career site. Remember the name is the public title that appears in the browser.
Expected outcome: A site creation form is open with name and code fields.
Set the languages
Select a default language for the career site. If the site should be available in several languages, click Manage Languages and select the others.
Expected outcome: A default language is set, with additional languages where required.
Choose a template or reuse content pages
Select a template. If custom content pages were created for another career site, select the ones to use; otherwise the template splash page is used.
Expected outcome: A template is selected, with content pages where available.
Set the context
Contextualize the career site using job requisition locations, organizations, job categories, job functions, recruiting types and job requisition flexfields. Within each context the OR operation applies; across all contexts you set, the AND operation applies. If an organization or location is the context, requisitions for that parent and for its child organizations or locations are posted.
Expected outcome: The site is scoped to a precisely stated rule.
Create the site
Click Create Site. The site is created with the status Inactive. Activation is a separate configuration step that is not described on the page this procedure is based on, so consult your own product documentation for it.
Expected outcome: The site exists with the status Inactive.
Run this procedure
Sign in to record a run. The steps above read the same either way; only the record needs an account.
Verify
A configuration that is not verified is not complete.
- Test the context against requisitions that should appear and requisitions that should not. Both directions matter.
- Confirm a child organization or location requisition appears when its parent is the context, because that is documented inheritance rather than a bug.
- Before activation, confirm no requisition appears that the organisation has not approved for external publication.
If it fails
| Symptom | Cause | Resolution |
|---|---|---|
| A site scoped to one country and one business unit shows requisitions from other countries. | The AND-across-contexts rule was applied as OR. | Narrow the context so every context set must match. Re-test against a requisition that matches only some contexts, which should be excluded. |
| A requisition for a child business unit appears on a site scoped to its parent. | Parent context publishes child requisitions by documented design. | Either accept the inheritance as intended, or set the context on the child organization instead of the parent. |
| The site exists and is configured but appears nowhere externally. | A newly created career site has the status Inactive. | Complete the activation step in your own product documentation, then re-test the context externally. |
| The site shows a generic template page instead of the content you designed. | No custom content pages were selected, so the template splash page was used. | Select the custom content pages created for another site, or accept the splash page as the intended outcome. |
Rollback
Configuration in a live tenant is reversible only if somebody wrote down how.
- Remove the context, or end-date the context values, to stop any requisition publishing to the site.
- If the site itself must be withdrawn from public view, return it to a non-active state. Consult your own product documentation for the permitted state transitions.
- Do not delete the site while requisitions or candidate applications reference it. Withdraw it instead.
Security notes
- A career site is public to external candidates. Context errors are disclosure risks, not only usability problems.
- Review every requisition that the context admits for confidentiality before activation, especially where job category or requisition flexfields are used as context.
- Restrict who can change a career site context, because the change takes effect on the next posting cycle.
What a career site contextualizes on
Configured contexts, read in order. Within one context the operation is OR; across the contexts that are set it is AND. Listed in order: Location context, then Organization context, then Requisition, then Career site.
A career site publishes the requisitions that match the context configured on it. Within a single context, for example location, the operation is OR: a requisition matching any one of the configured locations qualifies. Between the contexts that are set, for example location and organization, the operation is AND: the requisition must satisfy every configured context. So a site with one UK location and one UK Operations organization context publishes only UK requisitions in that organization. There is a second rule that catches people out: a parent context also publishes its children, so a site scoped to UK Operations will publish requisitions belonging to a child organization unless the organization context is narrowed.
Career site lifecycle
A career site moves through these states in order, and each transition is owned by a named actor.
A career site is created with the status Inactive, which means nothing is public from it yet. It is then configured: contextualization dimensions are chosen to select which requisitions qualify, and content pages are selected to control what the site looks like. If no custom content pages are selected, the template splash page is used as the fallback, so an unconfigured site looks generic rather than broken. The site is then activated, which is what makes the matching requisitions public. Activation is the point where a contextualization mistake becomes a public mistake, which is why the context should be tested against sample requisitions before activation rather than after.