Skip to content
Search

Roles and permissions

Each member holds one role, for the whole organization.

Everything. Administrator is the only locked role: it cannot be edited, renamed or deleted.

The working role, with 37 permissions.

  • Creates, edits and deletes items, attachments, comments, time logs, workload allocations, capacity entries and baselines.
  • Reads types, fields, views, users and teams.
  • Does not manage views, users, teams, types, fields or roles.

The following-along role, with 19 permissions.

  • Reads items, types, fields, views, users, teams, attachments, time logs, allocations, capacity and baselines.
  • May write comments and set its own notification preferences.
  • Nothing else.

Collaborator and Reader are ordinary roles. An administrator can rename, re-tune or delete them.

The Financial data row in the grid covers cost rates and the Budget field. Neither Collaborator nor Reader holds it, so only Administrator sees rates, budgets and cost at first. To share them with another role, set its Financial data row.

  • Read only shows the rates and every Budget. Read & write also lets the role change rates and budgets.
  • Teamhood never sends a role without Financial data the value of Budget, so its exports, the public API and the MCP server do not carry it either. Where a view shows Budget, the role sees a dash.
  • Cost figures need both Financial data and Time tracking set to at least Read only.

Anyone who can see cost can calculate a person’s rate from their cost and hours. How budgets and cost are calculated explains why, and how team rates keep pay private.

Settings → Organization → Roles is a grid with one row per thing that can be permitted, and one column per role. Open in Teamhood See Create a role.

Roles are assigned on Settings → Organization → Users, in the Role column. Open in Teamhood

Only an administrator may change a person’s role. If you move your own role away from Administrator, only another administrator can give the role back.