> For the complete documentation index, see [llms.txt](https://fotello.co/university/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fotello.co/university/teams/payroll.md).

# Payroll

Pay team members for completed work with product-based commissions.

Payroll pays your team a share of every job they shoot. Set a flat amount or a percentage on any product, and Fotello creates a payable task for the assigned team member each time that product is booked. Track what each member is owed and record what you've paid — all in one place.

Payroll is available to every Fotello account. Connect it yourself anytime, with no upgrade required.

### Turn on Payroll

{% stepper %}
{% step %}

#### Open the Payroll app

In your dashboard, go to **Apps**. Under **Apps by Fotello**, click the **Payroll** app.
{% endstep %}

{% step %}

#### Connect it

Click **Connect** to turn Payroll on for your team. Once connected, **Payroll** appears under **Operations** in your left sidebar with a **Tasks** tab and a **Payouts** tab, and a commission field is added to your products.
{% endstep %}
{% endstepper %}

### Follow the setup checklist

The **Settings** tab of the Payroll app opens with **Payroll setup**, a short checklist that walks you through your first payout:

1. **Set a commission on a product**, so Fotello knows what a job pays.
2. **Assign a team member to the job**, because every commission task needs an owner.
3. **Record a payout** to mark the work paid once the listing is delivered.

Each step ticks off on its own as you complete it, so you can see what is left at a glance.

### Set commissions for every product at once

Click **Set commissions** on the checklist to open **Product commissions**, where every package, service, and add-on is listed together with its price.

1. Use the search box to find a product, or the dropdown to show only **Packages**, **Services**, or **Add-ons**.
2. On each row, choose a flat amount or a percentage, then enter the value.
3. Leave a row empty to pay nothing on it.
4. Click **Save** when you are done.

### Set a commission on a single product

You can also set a commission while you edit a product.

1. Go to **Products** and open a product — a service, an add-on, or a package.
2. On each pricing option, find **Pay assigned member**.
3. Choose a flat amount or a percentage of the product price, then enter the value.
4. Save the product.

You can set a different commission on each pricing option. Leave it blank on any option that shouldn't pay a commission.

The **Settings** tab of the Payroll app also lists every product that currently pays a commission.

### How tasks are created

Once a product pays a commission, Fotello creates a task automatically every time that product is booked:

* The task goes to the team member scheduled for the shoot.
* When several team members shoot the same job, the commission splits evenly between them.
* The task completes automatically once the listing is delivered, and is canceled if the order is canceled.

### Tasks on a listing

Open any listing and select the **Tasks** tab to see the commissions tied to it. From here you can:

* Assign a task to a team member, or reassign it.
* Edit the amount on a task.
* Mark a task done when the work is complete, or reopen it.

Click **+** to add a task by hand — give it a name, pick the order, optionally assign a member, and enter a payout amount. Use this to pay for work that isn't tied to a commissioned product.

### Track every task

Select **Payroll** under **Operations** in the left sidebar and open the **Tasks** tab to see every commission in one list.

* Owners and admins see all tasks across the team, with an **Assignee** column.
* Photographers see only the tasks assigned to them.

Each row shows the listing, date, status, and amount. The heading totals what's currently unpaid and paid to date.

#### Task statuses

* **Unassigned** — waiting for a team member.
* **Pending** — assigned, work not yet finished.
* **Done** — work complete and ready to pay.
* **Paid** — you've recorded the payout.
* **Canceled** — the order or product was removed.

### Pay your team

When work is done, open the **Payouts** tab in **Payroll** to record what you've paid.

{% stepper %}
{% step %}

#### Find what is owed

The page opens with everything ready to pay. **Currently owed** at the top is the total across your team. Use the status, team member, and date range filters to narrow the list.
{% endstep %}

{% step %}

#### Select the tasks you paid

Tick the **Done** tasks you've paid. Only tasks that are done can be selected.
{% endstep %}

{% step %}

#### Mark them paid

Click **Mark paid**, then confirm the amount and who you paid. This records the payout in Fotello — you make the payment itself however you already pay your team.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Recording a payout can't be undone. Once marked paid, a task moves to the **Paid** status and drops out of what's owed.
{% endhint %}

### Pause Payroll

Use the **Disconnect** button at the top of the Payroll app to pause it. **Payroll** is hidden in the sidebar for your whole team, but your commission rules and existing tasks are kept, and everything comes back when you reconnect.

<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://fotello.co/university/teams/payroll.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.