Skip to content

Managing Teams in Testomat.io

Teams in Testomat.io help you organize your growing organization by grouping users together and managing access to multiple projects efficiently. Instead of assigning users individually to each project, you can now create Teams and assign them to any number of projects in just a few clicks.

This feature is critical for scaling organizations, improving permission control, and streamlining onboarding for new team members.

Why Use Teams?

  • Simplified access management: Assign an entire group of people to projects in one action — no need to manage access user-by-user
  • Clear structure: Organize users based on people’s roles, departments, or external teams
  • Consistent permissions: Ensure everyone in a specific role or team has access to the right projects — with a single assignment
  • Better control: Easily update access when people join, leave, or change teams
  • Visibility: See all projects and members connected to a team — all in one place

Testomatio - Teams

  • Onboarding new people quickly

When a new team member joins, simply add them to the appropriate team (e.g., QA Team), and they’ll automatically gain access to all relevant projects — no manual steps required.

  • Managing departments efficiently

In companies with several functional departments — like Backend, Frontend, QA, or DevOps — it’s common for each group to work on multiple projects. With Teams, you can reflect that structure: create one team per department and assign them to the projects they’re responsible for. For example, your QA team can be granted access to 5 projects at once — no need to assign each QA engineer individually.

  • Controlling access for contractors

Need to give external testers or developers limited access? Create a dedicated contractor team, assign only the projects they need, and manage their access independently from your core teams.

  • Supporting role changes and reassignments

When someone changes roles — for example, moving from QA to a Project Manager position — simply remove them from their current team and add them to the new one. Their project access will be updated instantly based on the permissions of the new team.

  • Temporary cross-functional initiatives

For time-limited efforts like major releases or audits, create a dedicated team (e.g., Release Task Force) and give them quick access to all related projects. When done, simply deactivate the team.

The Teams Dashboard provides a complete overview of all teams within your company — showing team names, members, assigned projects, and available actions like edit or delete.

This centralized view helps you stay organized and manage access efficiently.

To start organizing your teams and streamline access control, begin by creating your own team.

Teams Dashboard

To create a Team you need:

  1. Go to the ‘Companies’ page.
  2. Open your Company.

Testomat.io - Teams

  1. Click ‘Extra menu’ button.
  2. Select ‘Teams’ option from the list.

Testomat.io - Teams

  1. Click ‘Create New Team’ button.

Testomat.io - Teams

  1. Enter Team name.
  2. Click ‘Create’ button.

Testomat.io - Teams

Team is created and now you need to add Projects and Users to your new team.

To add Projects:

  1. Click ‘Add Project’ button.

Testomat.io - Teams

  1. Select projects from the list.
  2. Click ‘Add Project’ button.

Testomat.io - Add Project

Once added, all team members automatically gain access to these projects.

  1. Click ‘Add User’ button.

Testomat.io - Add User

  1. Select users from the list.
  2. Click ‘Add User’ button.

Testomat.io - Add User

You can also edit your Team, add/remove user or assign the Team to another project by editing it at any time later.

Namely, you can:

  1. Delete a team from a project by removing a project from the Team.
  2. Delete a user from the Team.
  3. Assign the Team to a project by adding a project to the Team.
  4. Add a new member to the Team.

Testomat.io - Edit Team

  1. Edit the Team name.
  2. Delete the Team.

Testomat.io - Edit Team

  • Regularly review team membership to ensure access remains up-to-date and relevant
  • Use clear and descriptive team names that reflect their roles or functions within your organization
  • Deactivate temporary teams once their projects or initiatives are completed to maintain a clean and organized workspace