> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/your-data-sources/deputy.md).

# Deputy

Connect Deputy to bring in your rosters and timesheets — and fix late and early clock-ons from Kula without opening Deputy. Pay rates never leave Deputy.

Deputy brings your **team's hours** into Kula Intelligence — who was rostered, who clocked on and off, which timesheets a manager has approved — so Kula can show you the fortnight's exceptions in one place, answer hours and lateness questions, and put the payroll hours in a file per company.

## What we read — and what we don't

* **We read:** your locations, employees, rosters (including shifts already published for the next four weeks), timesheets, leave and availability.
* **We never read pay.** Rates, costs, pay rules and awards are dropped before anything is stored, and nothing in Kula can show them. They stay in Deputy.

## What Kula changes in Deputy

Timesheets, and only when someone asks it to.

Kula's **Time entries** app shows the timesheets that need a manager's word — clocked on late, finished early, a missed clock-off. A manager can **revert to the roster**, **accept as clocked**, or **edit** a timesheet, and Kula makes that change in Deputy and approves it. Before it changes anything, Kula adds a **comment to the timesheet saying who changed it**. The original times, the new times and the reason are kept in Kula's History.

When someone goes home sick partway through a shift, a manager can also shorten the timesheet and book the rest as **leave**, after checking exactly what will be sent.

Nothing else is written to Deputy. Kula doesn't create or delete shifts, staff or locations, and it doesn't touch pay.

**Setting up and using Time entries**, step by step, is in [Time entries](https://docs.kula.digital/apps/time-entries.md). The app appears once Deputy is connected.

If the owner turns on **auto-approve** in Time entries → Settings, Kula also does this itself for timesheets within a few minutes (you choose how many) of the roster. It is **off until you switch it on**.

## What you'll need

* A **Deputy administrator login** — someone who can authorise connected apps for your Deputy account.
* About two minutes. There are no keys to create or paste — the connection is a standard **Connect with Deputy** authorisation, and your password never touches Kula.

## How to connect

1. In Kula, open **Connectors → Deputy** and click **Connect with Deputy**.
2. Sign in to Deputy and, if you have more than one, choose your **Deputy install**.
3. Review the access summary and **authorise** — Deputy sends you straight back to Kula.
4. Kula confirms the Deputy account it reached and queues the first import.

## What to expect after connecting

* **The first import starts at the next hourly sweep**, so within the hour. If you don't want to wait, open the connector's monitor page and click **Update to now**.
* It brings in about **3 months** of timesheets and rosters, and the **next four weeks** of published shifts. Older history can be loaded on request.
* After that Kula refreshes **every hour**, and a change in Deputy — a clock-on, an edit, a newly published roster — reaches Kula within seconds where Deputy tells us about it.
* **Tell Kula which Deputy location is which site.** Open **Time entries → Settings** and match each Deputy location to the studio's sites. Until you do, only the owner sees that location's timesheets; managers see their own site's once it is matched.
* **Tell Kula which company pays each person**, if you have more than one: **Time entries → Companies**. The payroll export is split by it. You can paste a list.

## Reconnecting

Deputy gives Kula a fresh key each time it refreshes the connection, so a connection that has been unused for a long time or revoked on Deputy's side needs authorising again. Click **Reconnect** on the connector's page, sign in and authorise. The import picks up where it left off.

## FAQ

**Does Kula see what I pay people?** No. Pay rates, costs and awards never leave Deputy. Kula works in **hours and times**.

**Can Kula change a timesheet without me knowing?** Not unless you have asked it to: a manager's fix is a click in Time entries, recorded with their name, the time and the reason; and auto-approve is off until the owner switches it on. Every fix, and every change made in Deputy by anyone else, is kept in the **History** tab, with before and after.

**What if I fix a timesheet in Deputy myself?** That's fine. Kula sees it within the hour (usually seconds) and records it as a change made in Deputy.

**I have two Deputy accounts.** One Kula org holds **one** Deputy connection. A second account needs its own Kula org — ask us to set it up.

**My staff are in more than one system.** Kula matches a Deputy employee to the same person in your booking system by **email and mobile number**. Someone with no matching email or mobile stays a separate record — that's normal.

## If it stops working

A Deputy error usually means the authorisation lapsed or was revoked on Deputy's side. Click **Reconnect** and re-authorise. See [Keeping your connectors healthy](https://docs.kula.digital/your-data-sources/operating.md).
