Toggl 2.0 Vocabulary
A quick-reference glossary for the terms used across Toggl 2.0 — Organizations, Workspaces, Clients, Projects, Tasks, Tags, and more.
User Account
Your account is connected to the email address you use to log in — shared across Toggl Track and Toggl 2.0. You can belong to several Organizations with one user account. Manage your account from Profile settings.
Organization
Organizations sit at the top of the data hierarchy, same as in Toggl Track. A single user account can belong to multiple Organizations, and subscriptions are tied to the Organization level.
Workspace
Everything you do in Toggl 2.0 — time logs, projects, clients, tasks, tags — is allocated to a Workspace. Most Organizations have one Workspace, though multiple Workspaces are possible on certain plans.
Roles
Access within a Workspace is role-based: Admin, Manager, Member, and Guest. Guest is available on Starter plans and above (not on Free). See User Roles in Toggl 2.0 for the full breakdown, and Guest Role in Toggl 2.0 for Guest specifically.
Two more roles exist at a narrower scope than the workspace: Project Manager and Team Lead (see Project and Teams below). See also Custom Roles in Toggl 2.0, below.
Custom Roles
An Enterprise-only feature: tailored permission sets built beyond the fixed Admin/Manager/Member/Guest roles, for organizations that need something more specific — a Finance Viewer who can see rates but not edit them, an External Contractor limited to their own assigned projects, and so on. Not self-serve — requested through your Customer Success representative, who configures the permission set for you. Each user holds one Custom Role per workspace. See Custom Roles in Toggl 2.0.
Teams
Toggl 2.0's equivalent of Toggl Track's "Groups" — a way to bulk-organize members so you can assign a whole set of people to projects or reports at once instead of adding them one by one. A Team Lead can be assigned to a Team from the Admin Console for someone who needs visibility across the group without a full workspace-admin role.
Client
Clients group Projects together. A single Client can have many Projects, but each Project can only have one Client. Time Logs can't be assigned directly to a Client — only through the Project it's linked to.
Project
The main container for related work. Dates, time estimates, billable rates, and fixed fees are all set at the project level. A Project can contain multiple Tasks and Time Logs. New projects are private by default; whoever creates a private project automatically becomes its Project Manager (a project-scoped role, distinct from the workspace-level roles above), and everyone else added defaults to Project User.
Recurring Project
A Project set to repeat on a schedule (weekly, bi-weekly, monthly, quarterly, or annually) instead of being rebuilt each time — each new period can carry over a fresh budget, with unused time or overruns rolled over according to the policy you choose. Once two periods are completed, Smart Estimates suggests a budget for the next period based on actual tracked time. See Set Up a Recurring Project in Toggl 2.0.
Task
A piece of work inside a Project — or, unlike in Toggl Track, a personal to-do with no Project at all. A Task can have an assignee, dates, a time estimate, priority, and a Status, and it's what the Timeline and Board views are built on.
Subtask
A Task nested one level under a parent Task. Subtasks are flat — a Subtask can't have its own Subtask. Time, estimates, and status are tracked independently of the parent Task.
Status
A customizable stage for a Task (e.g. To do / Doing / Done), shown as columns on the Board view.
Tags
Tags let you attach additional information to Tasks and Projects.
Custom Fields
Admin-defined metadata on Projects and Tasks. Stricter and more reporting-friendly than Tags, useful for things like billing codes or compliance categories. See Project-Level Custom Fields and Task-Level Custom Fields.
Time Log
The object that holds your time information — the Toggl 2.0 equivalent of a Toggl Track Time Entry. A Time Log can carry a description, project, task, and billable status, with only a start time required by default. Each one can represent time you've already worked (logged) or time you've scheduled (planned) — both show together on the Calendar.
Work Hours
A member's expected working schedule, set per person from Settings → Availability → Work Hours (or by an admin on their behalf): total weekly hours plus a daily pattern — no schedule, standard 8-hour, or custom per day. The pattern set determines how Capacity is calculated day to day — for example, a custom schedule with a 6-hour Friday counts as 6 hours of capacity that day, not 8; under a no-schedule or standard 8-hour preset, weekends aren't counted as work days. It's the baseline the Workload and Utilization reports measure logged time against. See Availability Settings: Time Off, Work Hours, and Public Holidays.
Capacity
How many hours a member has left to take on new work in a given period, shown on the Timeline as a percentage of their available time. It starts from their Work Hours, then subtracts anything already using up that time: tasks with estimates already assigned to them for the period, logged Time Off, Public Holidays, and — if they've connected a calendar — their scheduled meetings and events.
Milestone
A zero-duration marker on the Timeline for a key date — a launch, a client sign-off, a deadline.