> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/payroll/setup/work-locations.md).

# Manage work locations

Add, rename and delete the work locations that your production's payroll employees and timecards use.

Work locations are the addresses where your crew works. Manage them on the **Work Locations** tab of **Payroll > Setup**, which Owners, Super Admins and Managers see.

{% hint style="info" %}
If RollCredits payroll is turned on for your production, **Payroll > Setup** has a **Work Locations** tab. Until payroll setup is saved, Owners and Super Admins see the tab greyed out, and Managers see a note to contact a Super Admin in place of the tabs. See [Set up payroll](/payroll/setup.md).
{% endhint %}

The table shows each location's **Location Name**, **Street 1**, **Street 2**, **City**, **State** and **Zip Code**.

You need at least one work location before you can add employees. Until then, the **Employees** tab shows "You must create a work location before you can add employees" in place of **Add New Employee**.

## Add a work location

1. Select **Add New Work Location**.
2. In the **Add Work Location** panel, enter a **Location Name**, **Street 1**, **Street 2** if needed, **City**, **State** and a five-digit **Zip Code**.
3. Select **Confirm**, or **Cancel** to close the panel without saving.

RollCredits checks the address for payroll taxes before saving it. If it can't be used, the panel shows "Unable to add work location:" with the reasons, such as "Address is a PO Box." or "Address is not deliverable." Correct the address and select **Confirm** again.

If your state isn't in the **State** list, contact RollCredits support at <help@rollcredits.io>.

## Rename a work location

1. Select the **...** menu at the end of the location's row.
2. Select **Edit Location**.
3. Change the **Location Name** and select **Save**.

Only the name can change. To use a different address, add a new location, move employees' **Default Work Location** to it, then delete the old one.

## Delete a work location

1. Select the **...** menu at the end of the location's row.
2. Select **Delete Location**.
3. In **Delete Work Location**, select **Confirm**.

{% hint style="warning" %}
You can't delete a location that is any employee's default work location, so **Delete Location** is greyed out for it. Change those employees' **Default Work Location** first. Timecards that used a deleted location switch to the employee's default work location.
{% endhint %}

## Where work locations are used

* Every payroll employee has a **Default Work Location**, shown in the **Work Location** column of the **Employees** tab. See [Add and edit payroll employees](/payroll/setup/employees.md).
* Every timecard has a **Work Location**, which starts as the employee's default. While a timecard isn't approved, the reviewer can choose another location for that week. See [Review and approve timecards](/payroll/review-payroll-runs/review-timecards.md).


---

# 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://knowledge.rollcredits.io/payroll/setup/work-locations.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.