> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inploi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Job management

> Create, edit, approve, publish, schedule, and close jobs in Studio

# Job management

The **Jobs** area lists your roles and their status. Jobs move through a lifecycle, and the actions available on a job depend on its current status and on your [permissions](#permissions-and-access).

## Job statuses

| Status             | Meaning                             |
| ------------------ | ----------------------------------- |
| **Draft**          | Being prepared, not yet visible     |
| **Pending review** | Submitted and awaiting approval     |
| **Scheduled**      | Approved with a future go-live date |
| **Live**           | Published and visible to candidates |
| **Expired**        | Past its expiry date                |
| **Filled**         | Closed because the role was filled  |
| **Closed**         | Closed without filling              |
| **Deleted**        | Removed                             |

## Creating a job

Create a new job from the Jobs area. You start by entering the job title, then choose how to begin:

* **Create blank job** — start from an empty form, seeded with the title you typed.
* **Copy from existing** — as you type, Studio suggests recent jobs with similar titles. Pick one to copy its details (title, employment type, location, salary, and description) into the new job, then adjust from there.

Either way, fill in the remaining details and the new job starts as a **Draft**, so you can save your progress and come back to it before anyone else sees it.

<Note>
  Copying from an existing job creates a brand-new draft — it never changes the original. The go-live and expiry dates are **not** carried over, so set the [schedule](#scheduling-publication-and-expiry) for the new job yourself.
</Note>

You need permission to create jobs to do this — see [Permissions and access](#permissions-and-access).

## Editing a job

Open a job to edit its details. Drafts can be edited freely. You can keep refining a job until you are ready to put it forward for review.

<Note>
  Jobs that originate from a connected ATS are managed by that system and are read-only in Studio. You can view them, but the editing and lifecycle actions below don't apply.
</Note>

## Approving and publishing a job

Getting a job live is a two-step path so that someone reviews a role before candidates can see it:

<Steps>
  ### Submit for review

  From a **Draft**, choose **Submit for review**. The job moves to **Pending review**. If you change your mind, **Withdraw from review** returns it to Draft.

  ### Approve

  Someone with review permission opens the pending job and chooses **Approve**. What happens next depends on the job's go-live date:

  * With **no go-live date, or a date in the past**, the job goes **Live** immediately.
  * With a **future go-live date**, the job becomes **Scheduled** and publishes automatically when that date arrives.

  A reviewer can instead **Reject** the job — which sends it back to Draft with a reason for the author — or **Unschedule** a scheduled job to return it to Draft.
</Steps>

## Scheduling publication and expiry

Two optional dates control when a job is visible:

* **Go-live** — when the job should be published. Set a future date to schedule it; leave it empty to publish as soon as it is approved.
* **Expiry** — when the job should automatically retire. Leave it empty for an open-ended job that stays live until you close or expire it.

If you don't configure scheduling, jobs go live immediately on approval and do not expire on their own.

## Closing and removing jobs

Once a job is live (or earlier in its lifecycle), you can take it down or close it out:

| Action                    | Effect                                                                     |
| ------------------------- | -------------------------------------------------------------------------- |
| **Expire**                | Take a live job down once it has run its course                            |
| **Unpublish**             | Remove a live job from the site and return it to Draft (asks for a reason) |
| **Mark as filled**        | Close the role because it was filled                                       |
| **Close without filling** | Close the role without a hire (asks for a reason)                          |
| **Delete**                | Remove the job                                                             |

Some actions ask for a short reason. Reasons, and the actions taken, are captured on the job's audit trail so there is a record of how a role was handled.

<Note>
  Only the actions valid for a job's current status are offered. For example, **Approve** only appears on a job that is pending review, and **Expire** only on a job that is live.
</Note>

## Permissions and access

The actions you can take on a job depend on your role:

| Capability | What it allows                                                    |
| ---------- | ----------------------------------------------------------------- |
| **Read**   | View jobs and their details                                       |
| **Create** | Create new jobs                                                   |
| **Edit**   | Update jobs, submit for review, expire, mark as filled, and close |
| **Review** | Approve, reject, unschedule, and unpublish jobs                   |
| **Delete** | Delete jobs                                                       |

Job-level permissions also govern visibility, so people only see and act on the roles they are allowed to. See [Users and permissions](/studio/settings/users-and-permissions) for how roles are configured.

## Next steps

<CardGroup cols={2}>
  <Card title="Applications" icon="users" href="/studio/hiring/applications">
    Track and progress the candidates who apply to your jobs
  </Card>

  <Card title="Hiring overview" icon="briefcase" href="/studio/hiring/overview">
    What the Hiring section covers
  </Card>
</CardGroup>