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

# Jobs

A job is work that Membrane runs for you on an ongoing basis: reconciling every payout, triaging returns, keeping stock counts current. Where a question gets answered once, a job keeps producing results — on a schedule, in response to events, or when you ask for something.

## What a job is made of

* **A description** — what the work is and what outcome it promises.
* **Routines** — when the work happens: schedules and triggers that start it.
* **Deliverables** — the results it produces for you, each recorded and priced. See [Deliverables](/docs/how-membrane-works/deliverables).
* **An executor** — Membrane's built-in agent that performs each assigned task.
* **An operator** — the person accountable for the job and its results.

## The operator

A job is run by a crew — a team of operators, one of them accountable for the job and its results. Until the crew has that accountable operator, the job waits: routines don't fire and no results are produced. Who the operator is changes how much ceremony is involved:

* **You.** Say "I'll operate this job" and it's yours — no paperwork. You're taking accountability for a job that works for you.
* **Someone from your organization.** Assign them directly, the same way.
* **An external operator.** Someone outside your organization operates the job for you, under agreed terms and prices. That agreement is a contract, and the job starts only once both of you have accepted it — see [Operator Contracts](/docs/how-membrane-works/jobs/contracts).

When an agreement with an operator ends, the operator steps away and the job stops running — until you take it over, assign someone else, or agree with a new operator. Pausing is separate from any of this: switch a job off and it stops starting new work, switch it back on and it resumes — nothing is lost in between.

## How a job starts

Most jobs are drafted in conversation with the agent: describe the outcome you want, and it shapes the description, routines, and deliverables with you. The agent prepares everything, but taking on a job is always a person's decision — you become its operator, or you send it to one.

A job can also arrive as a proposal: an operator who found something worth handling in your operations drafts the job and proposes it to you, priced. Accepting it starts the job.

## Results and the conversation

Everything a job produces lands as [deliverables](/docs/how-membrane-works/deliverables) — recorded, reviewable, priced. The job also carries the conversation with its operator: ask about a result, request a change of scope, or discuss anything in between, right where the work happens.

## Permissions

New jobs are visible to the whole workspace by default: everyone can view them, and anything more requires a grant from the owner. Access follows the workspace permission ladder — see [Sharing and Permissions](/docs/how-membrane-works/sharing-and-permissions).

| Level      | What it allows                                                  |
| ---------- | --------------------------------------------------------------- |
| **View**   | See the job, its routines, and its tasks.                       |
| **Use**    | Launch work under the job — create tasks, run routines.         |
| **Edit**   | Change the job configuration, description, routines, and tasks. |
| **Manage** | Share, archive, or delete the job.                              |

Routines and tasks never hold their own grants — they inherit the job's sharing automatically, so sharing a job shares all of its parts at the same level.