Skip to main content
Every capability in TimeTracker, against every role. A check means the role holds it by default. A dash means it does not.

Role summary

Owner and Admin differ by exactly one capability: workspace.delete. Everything else an Owner can do, an Admin can do too.Client holds zero internal capabilities. A portal contact is not a member of your team. They see only what is shared with their own client company. That empty set is the portal firewall, and it cannot be edited.

The matrix

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

How to read this

Three things decide whether an action succeeds. This table covers only the first. A Project Manager holds time.approve, but only for people inside their scope. A capability is not a scope. See supervision scope.

Owner-exclusive capabilities

One capability can never be granted to another role, no matter how you build it: Granting ownership itself is also Owner-only. It is not done through the capability list at all – an Owner transfers it deliberately. See change someone’s role.

Capabilities that can be denied per person

Per-person overrides are deny-only. You can take a capability away from one person on top of their role. You can never use an override to grant something the role does not already include. See per-person permissions.

Capabilities a per-project role can widen

A person can hold a different role on one project. That per-project role is widen-only, and it reaches exactly one capability: Every other capability is decided by the workspace role alone. A per-project role can never take something away.

Which capabilities need a scope

These capabilities reach across people, so a supervision scope decides who they apply to. At scope None they have nobody to act on. 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 Everything else is about a thing, not a person. Closing a period, changing workspace settings and managing members are workspace-level administration.

Which roles can be invited

Every role except Owner can be assigned in an invitation. Ownership is never minted at invite time – an existing Owner transfers it. A Client can only be invited from that client company’s page, because a portal contact has to belong to a company. See invite a client contact.

Two roles have a locked capability set

The other five roles are editable, and you can build new ones. See custom roles.

Common questions

Yes, with a custom role. Copy the Member set, add time.approve, and give the role a supervision scope – otherwise the person has the permission and nobody to use it on.
Finance owns the money surface, not delivery. Invoices, payments, expenses, expense categories, the audit log and data export. It deliberately does not hold project or task management.
client.view is the only difference in that area. A Contractor tracks time and works tasks without seeing your book of business. They also lack the three report capabilities a Member holds.
No. rate.viewCost and time.viewCost stay with Owner and Admin by default, so internal pay data does not travel with delivery responsibility. A PM does hold rate.viewBilling – what you charge.
No. Owner is locked at every capability and at workspace scope. That is what makes it a guaranteed way back into your own workspace.

Capabilities reference

What each capability actually lets you do.

Supervision scope

The other half of every permission check.

Custom roles

Build a role that fits your team.

Per-person permissions

Deny-only exceptions for one person.

Roles and permissions

The model behind the matrix.

I cannot see a feature

Which of the four gates is closed.