Skip to main content
A capability is one named permission, such as time.approve. Roles are bundles of capabilities. This page lists all 66, in the same groups you see in the role editor. For the grid view of who holds what, see the roles and permissions matrix.

How to read the last column

A capability is not a scope. time.viewOthers says you may view other people’s time. Your supervision scope says whose. Both have to pass.

The 66 capabilities

Workspace

Members and roles

Clients, projects and tasks

Rates and cost

Time tracking

Timesheets

Time Clock

Work schedules

Budgets and money

Time off

Reports

Resource Planner

Integrations

The four that are not in the role editor

Four capabilities exist in the permission model but are not offered as checkboxes when you edit a role: They still apply everywhere else – the matrix above is what the product enforces.

Capabilities that only make sense with a scope

Fifteen capabilities reach across people. Granting one at supervision scope None gives someone a permission with nobody to use it on. The role editor warns you when that combination is set. time.viewOthers · time.editOthers · time.submitOnBehalf · time.reopenApproval · time.remind · time.approve · time.adjust · timecard.manage · timecard.approve · timecard.submitOnBehalf · timecard.reopen · leave.approve · leave.viewOthers · expense.approve · block.manageOthers

The three money-visibility capabilities

These decide which numbers a person sees, not which records. They are the most sensitive grants in the product, because two of them expose pay information. Reports enforce the same split. A report column that needs cost is dropped for a person who lacks the capability, and margin needs both cost and billing. See cost rates.

Common questions

No. The 66 are fixed. A custom role combines existing capabilities in a new way – it cannot create a new kind of permission.
report.edit covers reports the person built themselves. report.manage covers any saved report in the workspace, including other people’s.
client.view reads the client list and each client’s details. client.manage adds, edits and archives them. Anyone who can manage can already view.
They are different records. A timesheet is billable project time. A timecard is presence at work. Each has its own approval chain, so each has its own capabilities rather than riding on the other’s.
No. time.edit covers your own time. Changing a teammate’s entry needs time.editOthers, and that person has to be in your scope.

Permissions matrix

Every capability against every role.

Roles and permissions

How roles and capabilities fit together.

Custom roles

Pick capabilities and build your own role.

Per-person permissions

Switch one capability off for one person.

Supervision scope

Who a capability applies to.

Access errors

What each refusal message means.