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

# Settings and roles

> Configure workspace locations, units, team access, role permissions, and operations policies.

Settings control who can do work and which workspace defaults are used by [receiving](/receiving), [inventory](/inventory), [production](/production), [orders](/orders), [reports](/reports), and [QuickBooks handoff](/quickbooks-handoff).

## What to configure first

1. Workspace time zone. Operational timestamps use the workspace time zone unless a plant location overrides it.
2. Locations. Create receiving, storage, production, shipping, and quarantine locations before live lot work.
3. Units and conversions. Create unit codes used by item quantities, recipes, and lot movements.
4. Team and roles. Assign users only the access they need.
5. Production signoff policy. Define which roles must complete production signoff steps.
6. Import/export access. Confirm owners or admins will own setup imports.

## Location types

Batchlane commonly uses these location types:

| Type       | Use                                                            |
| ---------- | -------------------------------------------------------------- |
| Plant      | General facility or site context.                              |
| Receiving  | Where supplier lots arrive before putaway.                     |
| Storage    | Warehouse, cooler, freezer, dry storage, or packaging storage. |
| Production | Area where inputs are consumed and output lots are created.    |
| Shipping   | Finished goods staging or dock area.                           |
| Quarantine | Material that exists but should not be consumed or shipped.    |

Locations affect [Receiving](/receiving), [Inventory](/inventory), [Orders](/orders), and trace context in [Reports](/reports).

## Role guidance

| Role       | Typical access                                                         |
| ---------- | ---------------------------------------------------------------------- |
| Owner      | Full workspace, billing, team, and configuration control.              |
| Admin      | Day-to-day setup, imports, exports, roles, and operational correction. |
| Operations | Receiving, inventory, recipes, production, orders, and reports.        |
| QA         | Document upload/review, production release, traceability, and reports. |
| Bookkeeper | Reports and QuickBooks handoff.                                        |
| Viewer     | Read-only operational visibility.                                      |

Custom roles can be used when a workspace has specific separation of duties. If an action fails with a permission message, check this page first, then see [Common errors](/common-errors).

## Production signoff policy

Production signoff should match the team's real release process. A simple pattern is:

1. Operations completion confirms production actuals, waste, deviations, and output quantity.
2. QA release confirms required review before the batch record is treated as final.

Changing the policy affects future production runs. Existing signed records should remain stable for audit history. See [Production](/production) and [Documents and QA](/documents-qa).

## Setup errors to avoid

* Running imports before locations, units, and role ownership are clear.
* Letting every user act as owner or admin.
* Using QuickBooks setup as a substitute for clean operational records.
* Creating duplicate unit codes or location names that operators cannot distinguish.

Related pages: [Implementation checklist](/implementation-checklist), [CSV imports](/imports), [Address book](/address-book), [Common errors](/common-errors).