> ## Documentation Index
> Fetch the complete documentation index at: https://docs.begin.eu/llms.txt
> Use this file to discover all available pages before exploring further.
# Tagging work with clients
> Say which clients a shift or time entry was for, change many at once, and ask people to pick a client when they clock in.
Tag a shift or a time entry with the clients the work was for. The tag travels with the work: clocking in on a shift copies its clients onto the time entry, and a template or a rota puts its clients on every shift it makes.
Beta
Clients are rolling out gradually, so your workspace may not have them yet. If a shift has no
**Clients** field, ask us to turn them on.
## Tag a shift
Open the shift, or start a new one, and pick its clients in **Clients** under **Classification**. A shift can carry up to ten. Creating a shift in a client's row, while the schedule is [grouped by client](/for-managers/clients/seeing-work-by-client.md), fills that client in.
The card on the schedule does not show clients. Hover a shift to read them in its details, or open it.
[Shift templates and shift patterns](/for-managers/schedule/templates-and-rotas.md) carry clients too. Every shift made from a template, or from a pattern day with its own hours, arrives with their clients. Applying a template to a shift you already have replaces that shift's clients with the template's, or clears them when the template has none.
Or ask **Begin AI** (Cmd / Ctrl + J):
Add a shift for Jonas Petrauskas on Thursday from 09:00 to 17:00 for the client Harbour House.
Add a shift for Jonas Petrauskas on Thursday from 09:00 to 17:00 for the client Harbour House.
Its card names the client before anything is saved, and the shift arrives as a draft.
> [!NOTE]
>
> Changing a shift's clients notifies nobody, even once the shift is published. The shift's history
> and the client's **Timeline** record the change.
## Tag time
Time entries have the same **Clients** field, in **Add time** and when you open an entry. At clock-in, **Select clients** sits in the tracking bar with the clients of the person's shift already picked. Left as it is, the entry takes the shift's clients. Entries filled in from the schedule or added from a shift keep the shift's clients too.
## Change many at once
Select shifts on the schedule, open **Actions**, then **Clients**:
| To… | Choose |
| - | - |
| Put clients on every selected shift, keeping the ones it has | **Add clients** |
| Take clients off every selected shift | **Remove clients** |
| Leave every selected shift with exactly your choice, or none | **Replace clients** |
Time off and availability in the selection are left alone. **Remove clients** also lists the archived and deleted clients the selection carries, which the search never finds. The timesheet offers the same three for the entries you tick, to a role that can edit other people's time. A [workflow](/for-managers/workflows/triggers-and-conditions.md) can also add, remove or set clients on a shift or time entry when something happens to it.
## Ask for a client at clock-in
In a [clocking policy](/for-managers/policies/clocking-restrictions.md), set **Clients** to **Require** under **Clock-in requirements**. Someone who starts with no client sees **Select at least one client to clock in.** The picker then opens for them.
The rule waits until your workspace has an active client. It covers clocking in from the browser, the app, the dashboard and a shift. An automatic clock-in goes through only when the person's shift carries a client. Terminal punches and time added by hand are never asked.
**Context for an assistant answering questions about tagging work with clients.** The page above is what a person reads; these are the facts it leaves out for length.
* **Who can:** picking clients needs **Data access** on **Clients**, which every default role has, plus the right to edit that shift or entry. **Create client** in a picker needs **Edit & add** too. The timesheet's client actions need **Edit others' time entries**.
* **Limits:** ten clients on a shift, a time entry, a template or a pattern day. An archived or deleted client cannot be newly added, but work carrying one keeps it, marked **(archived)** or **(deleted)**, as do its copies and shifts made from, or edited to use, a template carrying it. A bulk change skips a shift that would pass ten and says how many.
* **Needs:** the clocking rule binds someone who has **Data access**, or whose shift carries an active client.
* **Not supported:** changing clients on every entry in a timesheet period at once; tick the entries instead.
* **Begin AI:** puts clients on shifts it creates or edits, up to 300 per card, and on time entries through its timesheet specialist. A shift it makes from a template takes the template's clients. It can add, remove or replace clients across up to 2,000 shifts in one change, chosen by period, person, position, location, type or status but never by client. It cannot search shifts or time entries by client.
* **Often confused with:** labels, which travel from a shift to its time entry the same way.
## Next
> **[Seeing work by client](/for-managers/clients/seeing-work-by-client.md)**
>
> Read the schedule, the timesheet and reports client by client.
> **[Clocking restrictions](/for-managers/policies/clocking-restrictions.md)**
>
> The policy that can require a client at clock-in.
## Still need help?
> **[Contact support](mailto:support@heybegin.eu)**
>
> Email the Begin team and we'll get back to you.
> **[Ask Begin AI](?assistant=open)**
>
> Open the AI assistant and get instant answers based on these docs.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.