> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/jobs/jobs-gerer-offres.md).

# Manage job postings

## List the offers

From **Jobs** > **Job offers** (`/app/jobs`), you can see all the organization's offers.

* The **HR users** see all offers, regardless of their status (draft, open, closed)
* The **standard users** only see open offers from the communities they belong to

You can filter offers by status, contract type, or community using the filter bar.

## Edit an offer

Click on an offer to see its details, then modify the desired fields:

* Title, description, location, contract type
* Communities (visibility)
* Enable/disable referral or internal mobility
* Offer status

## Change an offer's status

The possible status transitions are:

* **Draft → Open** : publishes the offer and makes it visible
* **Open → Closed** : archives the offer, it is no longer visible

A closed offer cannot be reopened. To republish it, you must duplicate the offer.

## Delete an offer

Deletion is permanent. Only HR users can delete an offer.

## View impressions

For each open offer, HR users can see who viewed the offer (employees and TV screens).

## Permission required

Editing, publishing, and deleting offers requires the **HR role**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.steeple.com/en/jobs/jobs-gerer-offres.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.