- Getting Started
- Time Tracking
- Monitoring & Productivity
- Desktop Timer Application
- Work Management
- Time Off & Scheduling
- Reports & Finance
- Integrations
- API
- FAQ
User Access Roles & Permissions
Last updated
What a role is
A role is a named set of permissions that decides what a member can see and do. Every member has one role that applies across the whole company, and can be given a further role on individual teams and projects. Roles are created and edited in Roles in the sidebar.
Every permission, what it allows, and which other permissions it needs are listed in Role Permissions.
Account roles
The account role is the one every member has, and it applies everywhere in the company. It is set on the member's profile in Staff, and it carries two things: the permissions that decide what the member may do, and the monitoring, notification, and wellbeing settings that override the account-level defaults for everyone holding that role.
A member has exactly one account role, changing it takes effect immediately and everywhere, and it is the only role that contributes settings and productivity rules.
The default roles
A new company starts with three roles. Rename them, change their permissions, or add your own.
- Owner — Holds every permission in the company. It cannot be deleted, and only the account owner can see or edit it.
- Manager — Runs the company day to day: staff and invitations, teams, clients and projects, tasks, other people's timesheets, reports, invoices, leave approval, and the company dashboard and Insights.
- Employee — Tracks their own work and nothing more: the personal timesheet, the web and mobile timers, leave requests, their own pay stubs, and the tasks assigned to them.
Team and project roles
A member can also hold a role on a particular team or a particular project, alongside their account role. Pick it in Role in the team on the team's member list (see Teams) or in Role in the project on the project's Assigned People tab (see Projects). Both start out set to the member's account role, so assigning someone changes nothing until you choose a different role for them.
Use these roles to give somebody more authority over one part of the company without widening what they can do everywhere else.
A team or project role only grants the permissions that describe work belonging to a team or a project — managing tasks, worklogs, and leaves, reviewing other people's time, editing the team or project itself, assigning project members, and reaching the company dashboard, the leave calendar, and Insights for it. A permission over something company-wide, such as managing staff or editing the organization's settings, does nothing when granted this way, because what it controls does not belong to a team or a project.
On the project's Assigned People tab, the role icon beside each member shows a This user can: tooltip listing exactly the permissions their project role grants there.
How permissions from several roles combine
Permissions add up, and they never subtract. When Trackabi checks whether a member may do something, it asks their account role first, then the role they hold on the team the work belongs to, then the role they hold on the project. The first role that allows the action settles it.
A member therefore always keeps everything their account role grants. A team or project role can only add to that, so taking a permission away from someone means editing the role that grants it — putting a narrower role on top of it will not do it.
Client users are the exception. Their access is judged against their account role alone, so giving a client user a team or project role changes nothing. See Clients.
Limiting a manager to their own team or project
To put someone in charge of one team or one project without handing them the whole company, give them a narrow account role and add the wider role only where it applies.
- In Roles, confirm that the account role you intend to give them does not already carry the company-wide permissions you want to withhold, such as managing staff or reviewing everyone's time.
- Assign that role to them in Staff as their account role.
- Open the team in Teams and set their Role in the team to Manager — or open the project, go to Assigned People, and set their Role in the project.
They now manage that one team or project and nothing else.
Editing a role
Open Roles in the sidebar and select a role. Each role has three tabs: Name and settings, Permissions, and Productivity rules. A new role has only the first tab until it is saved; the other two become available afterwards.
A role cannot be deleted while any member still has it, and the Owner role cannot be deleted at all. Only the account owner can see or edit the Owner role.
Name and settings
The tab holds the role's Role name and optional Comments, followed by settings that override account-level settings for everyone who has this role as their account role. Team and project roles never contribute settings: they come from the account role only.
Every setting on this tab is a three-way choice:
- As global (…) — Follows the account-level setting. The value in parentheses shows what that setting is right now, so a role left on As global (Disabled) turns on by itself if the account setting is later enabled. This is the default for a new role.
- Enabled — Turns the feature on for this role regardless of the account setting.
- Disabled — Turns it off for this role regardless of the account setting.
If your plan does not include a feature, its setting shows Disabled and choosing another value opens the subscription window instead of changing it.
User monitoring
- Screenshot capturing — Enables or disables screenshot capturing for this role, overriding Screenshot capturing in Settings > Time tracking > Screenshots & live view (see Screenshot Capturing).
- Require Minimum Time Logged — Requires users in this role to log a minimum amount of time, overriding Settings > Time tracking > Rules & limits. The first field chooses the period: Disabled, As global (…), Daily, or Weekly; the second sets Hours per day or Hours per week. Weekends and holidays are excluded, and a weekly requirement is checked on the last working day of the week.
- Limit Maximum Time Logged — Caps the time users in this role can log per day or per week, overriding Settings > Time tracking > Rules & limits, with the same period and hours fields. Time entries that would exceed the limit are rejected.
- Application activity and browser URL tracking — Enables or disables tracking of active applications and browser URLs for this role, overriding App activity & browser URL tracking in Settings > Time tracking > Auto-tracking (see App & URL Tracking).
- User activity score — Enables or disables the keyboard-and-mouse activity score for this role, overriding User activity score in Settings > Time tracking > Auto-tracking (see User Activity Score).
For the two time limits, leaving the hours field empty keeps the account's hours while the role sets only the period; hover the info icon beside the field to see the account value. Hours are entered as H:MM. A daily value must be under 24:00, a weekly value may go up to 168:00, and the maximum can never be lower than the minimum — when one is daily and the other weekly, the weekly figure is divided by the number of working days in your week for the comparison.
Notifications
- Summary emails — Enables or disables summary emails for this role, overriding Settings > Notifications. Recipients also need the View insights permission, because the emails carry Insights data (see Notifications (Summary Emails)).
Wellbeing
- Mood tracking — Prompts users to share how they feel by choosing one of five moods. The second dropdown, Mandatory or Not mandatory, decides whether they must answer at least once per working day before they can use the system.
- Impact tracking — After a mood is chosen, asks what impacts it most. Its own Mandatory / Not mandatory dropdown decides whether that answer is required.
- Comment — Adds a free-text step where users describe what is influencing their mood.
Impact tracking, the comment step, and both Mandatory options depend on Mood tracking. Setting Mood tracking to Disabled sets all of them to Disabled; setting any of them to Enabled sets Mood tracking to Enabled (and enabling Mandatory for impact also enables Impact tracking). How the prompts look and where the data is shown is described in Wellbeing Analysis.
Default project
Default project puts new time entries and timers started without a project into this project, for users with this role who can already log time in it; it never assigns anyone to the project. A default project set on a user's own profile takes precedence (see Staff (Users)). While a role uses a project as its default, the project cannot be archived or deleted.
Permissions
Tick the actions users with this role may perform, grouped as Organization, Staff, Time Tracking & Reports, Clients & Projects, Wages & Billable Amounts, Invoices, and Payroll. Every permission, what it allows, and which other permissions it needs are listed in Role Permissions.
Productivity rules
Rules on this tab decide which applications count as productive or unproductive for users with this role, and they take precedence over the account-level rules in Settings > Productivity. Each rule has Enabled, an Application type (Productive, Productive (ignore inactivity), Unproductive, or Untracked), a Match type (Contains or Exact match), and a Value to match against the application name. Click Add new to add a row and Save to apply.
A Value must be at least three characters and unique within this role's list; the comparison ignores case. The tab lists only the rules created for this role — account rules and Trackabi's default rules still apply to its users, so an empty tab does not mean they have no rules.
Role rules are taken from the user's account role, not from a team or project role. For what a rule is and how to write one, see Productive vs Unproductive Time; for the order in which role, account, and default rules are checked, and how to override one, see How Productivity Rules Are Applied.