Teams
Configure teams to limit access to projects and customers
Teams allow you to organize your users in groups and limit access to customers and projects.
A team consists of teamleads and regular team members. The teamleads have access to all contents and timesheets of the team. Every content object can be linked to an arbitrary amount of teams.
Limit access with teams
If you want to limit the access to Kimai functionality instead of content, please read the permissions documentation.
Once a team is assigned to a customer or project, access to this object and its children is limited.
Some examples how team assignments work:
- A customer without a team is visible to all users
- A project without a team, whose customer has no team is visible to all users
- A project without a team, whose customer is linked to Team B is only visible to all members of Team B
Please review the permission docs for customer, project and activity.
Permission details
First, we will have a look at the available user roles and how their permission work when using teams (this only applies when you use the default permission configuration):
System-Admin- can see and manage all content and use all administrative functions.Administrator- can see and manage all content, but access to system specific settings and contents (like users) are limited.Teamlead- can see all un-privileged contents and all contents assigned to his teams. Team specific contents can be managed for all teams where this user is theTeamlead.User- can see all un-privileged contents and all contents assigned to his teams.
Next step is to understand the difference between the user role Teamlead and the teamlead of a user team:
- The
Teamleadrole limits access to features likeedit,delete,budget - The leader of a team (
teamlead) is allowed to see team related contents likeprojectsandtimesheet
Contents:
Customers- access can be limited by assigning one or more teams. Customers without any team assignment can be seen by every user. Projects for this customer will be limited as well, if a team is assignedProjects- access can be limited by assigning at least one team. Projects without any team assignment can be seen by every user, which has access to the related customer
Create a team
Team creation is by default limited to the user roles System-Admin and Administrator.
Open System → Teams and click Create. Give your team a name and select the users you want to include. Each team must contain at least one user.
After adding your team members, select who will act as team lead by ticking the box next to their name. You can assign multiple team leads by selecting multiple boxes.
Users without the Teamlead role can be chosen as well, those are different.
In this context, team lead refers to a user’s position within the team hierarchy.
This is not the same as the Kimai Teamlead user role, which carries feature permissions.
Deactivated users
Deactivating a user does not change their team memberships:
- The user can no longer log in, neither in the web interface nor via API, so they lose access to all team contents
- The user stays a member of their teams, existing timesheets remain visible to the teamleads
- When editing a team, deactivated members stay in the member list and are not silently removed on save
- Deactivated users can not be added as new team members, they are not offered in the user selection
- Everyone who can edit the team can remove deactivated members, e.g. to clean up after an employee left
- Re-activating the user restores the access through all teams they are still a member of
Filter and search
You can query for a free search term, which will be searched in the fields:
name
Permissions
| Name | Description |
|---|---|
view_team |
View the Teams administration at System > Teams |
create_team |
Create new teams |
delete_team |
Delete existing teams |
edit_team |
Edit team assignments |
view_team_member |
View team leader and members for the teams of the current user |
Read how to assign these permissions to your user roles in the permission documentation.