A job always has a workflow state, which impacts its visibility on the frontend.
A site admin is able to change the job to any state. An employer can only follow certain state transitions according to the job checkout and publishing workflow.
|
Status |
Description |
|
Draft |
A job posting is created, saved for the first time but not published. This state is used when an employer starts the job posting workflow but does not complete the checkout. A job in the state "Needs review" is only accessible by admins and the owner organisation. A job with the status "Draft":
|
|
Needs review |
The job checkout has been completed, but the system is configured that every job needs approval by the site administrator before being published (e.g. used for job import if jobs from feeds should not go automatically live). It's also possible to configure that self-service jobs, i.e. jobs posted directly by employers, require a review. A job in the state "Needs review" is only accessible by admins and the owner organisation. A job with the "Needs review" state:
Important: If this workflow is enabled, then each job that is edited after it went live (either by an employer or via an automatic update of an XML job importer) will be sent back to "Needs Review". In order to avoid this in the case of XML job importers, check out our article here. |
|
Queued (for publishing) |
The job posting is ready (checkout completed), but the job start date is in the future. The system will automatically change the state to published once the publish date is reached. This is not a state a user can explicitly set. A job in the state "Queued" is only accessible by admins and the owner organisation. A "Queued" job:
|
|
Published |
The job is published (accessible to everyone in the www) and open for job applications. A "Published" job posting is a job that:
|
|
Unpublished |
The expiration date has been reached, therefore the job is removed from the search, Google/other search engines, and the applications are closed. A landing page is still accessible via a URL but has a warning that the job has expired. Moreover, by default, only the first few lines of the job description are shown. The job is not indexed and does not have any metadata info. The job is no longer available to the outside, but instead of deleting, the content is kept (e.g. for referencing job applications or for later re-publishing). The importer will set the jobs to unpublish if it is removed from the feed. The importer will republish them if they are added back to the feed. Jobs in the "Unpublished" state:
To republish a job, it has to be edited and the user needs to hit the "Publish" action again. If the user edits a job and only clicks "Save" the job will obtain the status “Draft” again. |
|
Archived |
A job in state "archived" is only accessible by admins and the owner of the organisation. An archived job can be re-published though, but the transition should always go through the "Unpublished" status. For example, only unpublished jobs can be archived and archived jobs will get an unpublished status once unarchived.
Jobs in the "Archived" state:
|