← Blog

Guide

Teams: who works with whom

Set up nested teams with a manager and members, then put records in a team with a related record field.

This is part of Qorekit 0.3, out now as a beta: download 0.3.0-beta.1. As with any beta, keep a backup of anything you cannot afford to lose.

Qorekit 0.3 adds teams. You can describe how your company is organised, with teams inside teams, and then say which team each record belongs to.

This post walks through setting up teams and connecting them to your records. The examples use a Sales module with Companies, Contacts, Deals and Activities, like the one in the public demo.

Where teams live

Teams are kept in Administration › Teams. A team has four things:

  • a name, such as Sales;
  • a manager;
  • members, the people who work in it;
  • the team it is part of, if any.

People who manage users also manage teams. Everyone else can see the teams, because they need to pick one on a record.

Building the tree

Teams nest the way your company does. A sales department with offices in two cities might look like this:

  • Sales
    • London
    • Berlin

To build it:

  1. Open Administration › Teams and choose New team.
  2. Name it Sales, pick its manager and add its members. Save.
  3. Choose New team again, name it London, and set part of to Sales.
  4. Do the same for Berlin.

The list shows each team under the team it is part of, so the tree is visible at a glance. The pencil beside a team changes it, and the bin moves it to the trash.

Qorekit keeps the tree sound. A team cannot be part of itself, and it cannot be part of a team below it. You cannot end up with Sales inside London inside Sales.

People in more than one team

Each team keeps its own list of members. Someone who works for both offices can be a member of London and of Berlin. When they filter by their own teams, they get the records of both, as the next sections show.

Putting records in a team

Teams are an entity like any other, kept in the system module. That means a record joins a team the same way it links to a company or a contact.

  1. Open the entity whose records belong to teams, such as Deals, and choose Design.
  2. Add a related record field that points at Teams. Call it Team.
  3. Save the field.

From then on, each deal has a Team field. People pick London or Berlin when they add or change a deal, as they would pick a company.

You can add a team field to as many entities as you like. Deals and Activities might both have one, while Companies, shared by everyone, have none.

Finding a team’s records

A team field works in filters like any related record field. It also offers one extra value, My teams, which finds the records of the teams the person looking is a member of.

This lets one saved view, such as My team’s deals, serve everyone. The London office sees London deals and the Berlin office sees Berlin deals, from the same view. The post on filters for my team shows how to set this up as a filter and as a quick filter.

Your own fields on teams

Since teams are an entity, you can give them fields of your own. A team might need a phone number for its office, or a region. Choose Design on the teams entity to add them.

The built-in fields stay: name, part of, manager and members. You can add to them but not remove them.

Teams and permissions

Teams describe who works with whom, and they make filtering by team easy. What a person may see and change still comes from their roles. To check what someone’s roles add up to, read what can this user do.

Read more

The teams page of the documentation has the details. Teams arrive with Qorekit 0.3.0.