Public or Private Career Sections
Career Section administrators can configure the Display Type property to designate a career section as public or private. A URL that does not include a precise career section code cannot lead candidates to a career section whose Display Type property is set to Private.
The Display Type property can be used to do two things:
Career sections created to gather additional information from candidates selected for a job or involved in an offer process can be configured such that they will be unavailable to other, "uninvited" candidates (Display Type: Private).
It is possible to "hide" a career section from the sitemap (job scraping) feature (Display Type: Private).
A career section's Display Type property can be set to Private to automatically exclude the career section from the logic used to resolve the Click Here link URL variables in message templates.
Most of the text in this section provides context and explanations regarding the first point.
Ensuring "uninvited" candidates are not directed to career sections created to gather additional information from candidates selected for a job or involved in an offer process.
URLs may or may not include a career section code. An example of a URL that includes a career section code is: https://zone.taleo.net/careersection/ex/jobdetail.ftl?job=1500123 where "ex" is the career section code and "1500123" is the requisition number. An example of a URL that does not include a career section code is: https://stghere.taleo.net/careersection/jobdetail.ftl?job=1500123. Two examples of URLs that do not typically include a career section code are jobs posted on job boards and URLs sent to Job Distribution Enablement (JDE) integrators.
URLs that do not include a career section code use the sequence order as displayed in the Sequence column in the list of career sections (Configuration > [Career Section] Administration > Career Sections) to direct candidates to the most appropriate career section.
For example, a URL that does not include a career section code typically brings external candidates to the external career section that has the lowest sequence number among the career sections on which the job is posted. Similarly, if the system identifies candidates as internal, the system directs them to the internal career section that has the lowest sequence number among the internal career sections on which the job is posted.
Organizations might have situations where their recruiters want to invite selected candidates who completed a job submission through a public career section to visit a second career section to provide additional information (e.g. social insurance number, date of birth) that might be required for background screening or other pre-hire steps. Requisitions might have been "unposted" (removed) from the public career sections but they could continue to be posted on the second career section for the purpose of gathering additional information from candidates selected for a job or involved in an offer process. How can organizations ensure that candidates who access a URL that does not include a career section code are not directed to a career section intended only for candidates who receive an invitation to provide additional information?
One method involves configuring the second career section (the one for requesting additional information from selected candidates) such that it has the highest sequence number among the career sections. Although this method can be very effective, if the second career section is the only place where the job is posted at a point in time, it will necessarily have the lowest sequence number among the career sections regardless of its number as displayed in the Sequence column. In such a case, some candidates who did not receive an invitation to visit the career section might land on the career section nonetheless. This might happen when:
URLs do not include a precise career section code and are published on job boards or at other locations.
Integrations are designed to pull all postings on external career sections.
A second, additional method consists of configuring the second career section as private. When external candidates access a URL that does not include a precise career section code, the system examines the external career sections that the job is posted on and selects the one that has the lowest sequence number while excluding all private career sections. Similarly, when internal candidates access a URL that does not include a precise career section code, the system examines the internal career sections that the job is posted on and selects the one that has the lowest sequence number while excluding all private career sections. To summarize, a URL that does not include a precise career section code cannot bring "uninvited" candidates to a private career section.
The second method also prevents job boards and web crawlers from indexing a career section.
Configuration
Administrators configure a career section as public or private through the Display Type career section property.
| Property Name | Location |
|---|---|
| Display Type | Configuration > [Career Section] Administration > Career Sections > (click career section) > [Properties] Edit |
The Display Type setting can be configured for external and internal career sections.
Because the Display Type property is not new, at migration the value (Public or Private) specified for each career section is maintained. However, if candidates or new hires click a career section URL that does not include a career section code, they will not be directed to any career section whose Display Type is Private.