> ## 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 projects
> Put a project, and one of its milestones, on shifts and time entries, require a project, and choose where projects are used.
Tag a shift or a time entry with the project the work is for, so the project's page lists it and its hours count against the budget. Each one carries a single project. The tag travels with the work: clocking in on a shift picks its project for you, and a template or a shift pattern puts its project on every shift it makes.
Beta
Projects are rolling out gradually, so your workspace may not have them yet. If **Projects** is
missing from the sidebar, ask us to turn them on.
## Turn projects on where you use them
Both switches start off. Go to **Settings → Projects** and turn on **Time entries**, **Shifts** or both under **Use projects in**.
| Turn on… | And projects appear in… |
| - | - |
| **Time entries** | Time entries, **Add time**, the tracking bar and clock-in, the timesheet's filter, column and grouping, and a project's **Timesheet** tab |
| **Shifts** | Shifts, shift templates and shift patterns, the schedule's filter, grouping and cards, and a project's **Schedule** tab |
You can turn a switch off again. Work already tagged keeps its project, and it shows again when you turn the switch back on. Reports still filter and break down hours by project. Workflows and Begin AI put no project on work where a switch is off.
## Tag a shift
Open the shift, or start a new one, and pick its project in **Project** under **Classification**. **Your projects**, the ones you lead or work on, come first, then **Projects**, then **Closed** for completed and cancelled ones. **No project** takes it off. Creating a shift in a project's band, while the schedule is [grouped by project](https://docs.begin.eu/for-managers/projects/seeing-work-by-project.md), fills that project in.
Hover a shift to read its project, or choose **Project** for a card's **Top field** or **Bottom field** under **Display**. [Shift templates and shift patterns](https://docs.begin.eu/for-managers/schedule/templates-and-rotas.md) carry a project too: every shift made from a template, or from a pattern day with its own hours, arrives with it.
To change many shifts at once, select them, open **Actions** and choose **Set project**. Every selected shift gets the project you pick, and **No project** takes it off. Time off and availability are left alone.
Or ask **Begin AI** (Cmd / Ctrl + J):
Add a shift for Jonas Petrauskas on Thursday from 09:00 to 17:00 for the project Harbour café refit.
Add a shift for Jonas Petrauskas on Thursday from 09:00 to 17:00 for the project Harbour café
refit.
It shows a card to confirm first unless your approval mode applies changes automatically, and the shift arrives as a draft.
## Tag time
Time entries have the same **Project** field, in **Add time** and when you open an entry. At clock-in, **Select project** sits in the tracking bar and in the **Time tracking** widget on the dashboard, already holding the project of the person's shift. An entry added from a shift takes the shift's project too. Clock-in takes only an open project: a completed or cancelled one is refused.
On the timesheet, tick entries and choose **Set project** to change them together; it needs a role that can edit other people's time. A [workflow](https://docs.begin.eu/for-managers/workflows/triggers-and-conditions.md) can also set or clear the project on a shift or time entry when something happens to it.
## Add a milestone
A shift or time entry can also carry one of its project's [milestones](https://docs.begin.eu/for-managers/projects/planning-projects.md#mark-the-way-with-milestones), so you can see which step of the project the work went to. Milestones start off. In **Settings → Projects**, turn on **Time entries**, **Shifts** or both under **Use milestones in**. Each switch works only while projects are on for the same place.
Once a project is picked, **Milestone** appears under **Project**: in a shift's **Classification**, in **Add time** and an open entry, in the tracking bar and in the **Time tracking** widget. It lists the project's milestones in order, done ones included, and **No milestone** takes it off. Picking another project clears the milestone. Clocking in on a shift, or adding time from it, takes the shift's milestone along with its project.
## Require a project
For planning, open **Policies → Schedule** and set **Require a project** to **Require** under **Requirements**. A shift then needs a project before it can be created or changed. Open shifts, time off and availability are exempt, and a bulk change that would clear a required project leaves that shift as it was.
For reporting, set **Project** to **Require** in a [clocking policy](https://docs.begin.eu/for-managers/policies/clocking-restrictions.md). It covers clock-in and **Add time**, and a linked shift fills its project in. An automatic clock-in goes through only when the shift carries a project; terminal punches do not ask for one.
Both rules wait until projects are on for that surface, your workspace has an open project and the person can see projects. When someone else saves the shift or time for them, that person must be able to see projects too, or the rule does not ask them for one. Time linked to a shift that carries a project is held to the reporting rule either way. The empty field shows what to supply and which policy requires it.
**Context for an assistant answering questions about tagging work with projects.** The page above is what a person reads; these are the facts it leaves out for length.
* **Who can:** picking a project or a milestone needs **Data access** on the role's **Projects** row, which every default role has, and the right to edit that work. The timesheet's **Set project** needs **Edit others' time entries**. **Use projects in** needs **Projects settings**.
* **Limits:** one project per shift, time entry, template or pattern day. A deleted project cannot be newly added; work that carries it keeps it, marked **(deleted)**. A completed or cancelled project can still be picked on a shift or entry from **Closed**, but not at clock-in.
* **Needs:** a paused project counts as open. A role without Projects **Data access** sees no project on tagged work and cannot change one.
* **Not supported:** more than one project on a piece of work, or a **No project** choice in the schedule's or timesheet's filter. Terminal punches copy the linked shift's project.
* **Milestones:** one per shift or time entry, always one of its own project's. They need the **Use milestones in** switch for that place as well as **Use projects in**. Changing the project, **Set project** on many items included, clears the milestone. Templates, shift patterns and copied or pasted shifts carry none. A deleted milestone shows as no milestone. Nothing filters, groups or reports by milestone yet.
* **Begin AI:** sets or clears the project on shifts, time entries and templates it creates or edits, up to 300 per card, and sets it on rota days. On shifts and time entries it also sets or clears the milestone, and it turns **Use milestones in** on or off with a card. It can change the project on many shifts or time entries in one card, as **Set project** does on the page. It follows and sets **Require a project** in schedule policies and **Project** in clocking policies, and changes **Use projects in** with a card. It cannot select work by project.
* **Often confused with:** clients, which record who the work was for. A shift or entry can carry both.
## Next
> [card] [Seeing work by project](https://docs.begin.eu/for-managers/projects/seeing-work-by-project.md)
>
> Read a project's shifts, time and hours against its budget.
> [card] [Clocking restrictions](https://docs.begin.eu/for-managers/policies/clocking-restrictions.md)
>
> Require a project when people clock in or add time.
## Still need help?
> [card] [Contact support](mailto:support@heybegin.eu)
>
> Email the Begin team and we'll get back to you.
> [card] [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.