---
title: "Teams"
slug: admin/teams
url: https://projectri.com/docs/admin/teams
section: admin
audience: admin
app_route: "/[slug]/admin/teams"
permissions: [team.view, team.manage]
mobile: "/admin/teams"
updated: 2026-09-08
source: Projectri documentation
---

# Teams

Groups of people inside a department, with their own name, colour and roster.

![Teams](https://projectri.com/docs-shots/admin-teams.png)

## What it is

A team is a named group of people that belongs to a department. Teams give the
workspace a second axis to the org chart: a department is the structural unit
that rarely changes, and a team is the working group that can change between two
meetings.

## How to get there

**Admin → People → Teams**. The console needs the ADMIN role. Reading teams and
departments is `team.view`; creating, editing, deleting a team and changing its
roster are all `team.manage`.

## How to use it

### Create a team

1. Press **New team**.
2. Give it a **Name** (required) and an optional one-line **Description**.
3. Pick a **Department** — required, and the list is the departments this
   workspace already has.
4. Pick a **Colour** from the eight swatches. It is what the team's tile is
   drawn in.
5. **Create team**.

### Add and remove people

1. Click a team row. The detail panel opens beside the list, or as a sheet on a
   narrow screen.
2. Use the picker at the bottom of the panel to add somebody. The list is the
   workspace roster minus the people already on this team.
3. The row appears at once, then settles when the server confirms. If the add is
   refused — they are already on the team, or no longer a member of the
   workspace — the row is taken back out and the reason is shown.
4. Remove somebody with the control on their row.

### Rename, recolour or re-file a team

1. Open the team, then press the pencil in the panel header.
2. The same form as creation opens with the current values. Changing the
   department moves the whole team under it.

### Delete a team

1. Open the team and use the delete control in the panel.
2. The confirmation says what survives: *"Its members keep their workspace
   access and their work."*

## What it affects

- **Adding somebody to a team notifies them.** It is the same event whichever
  screen it was done from.
- **Workload** lists each person's teams alongside their department, and reads
  them through the team's department — so a team whose department has been
  deleted stops being listed there.
- **The workspace directory.** The Team screen in the main app is the same
  people, read from the member's point of view.
- **Deleting a team removes only the grouping.** Nobody loses workspace access,
  project membership, or any work they did.

## On mobile

The **Teams** screen in the app's Admin hub lists the teams, and tapping one
opens its roster, its edit form and its delete in a sheet. Rosters are fetched
when a team is actually opened rather than up front.

Departments stay on the web, so a workspace with no departments cannot create a
team on the phone — the screen says so rather than offering a form that would be
refused.

## Limits and gotchas

- **A team cannot exist without a department.** The department is what scopes a
  team to a workspace, so the create form requires one and refuses to submit
  without it. Create the department first on
  [Departments](/docs/admin/departments).
- A team whose department has been deleted is hidden from this list. Its edit
  form falls back to an empty department rather than pre-selecting an id the
  dropdown cannot show.
- Only members of this workspace can be added. Somebody removed from the
  workspace cannot be added to a team.
- Deleting a team is immediate and has no undo. Deleting a *department* does
  offer one — see [Departments](/docs/admin/departments).

## Related

- [Departments](/docs/admin/departments) — the container a team must belong to.
- [Members](/docs/admin/members) — the roster teams are built from.
- [Workload](/docs/admin/workload) — where a person's team and department are read.
- [Team directory](/docs/workspace/team) — the same people, from a member's side.

## Related

- [Departments](https://projectri.com/docs/admin/departments.md): Company-level master data — the departments teams and members are filed under, shared across every branch.
- [Members](https://projectri.com/docs/admin/members.md): The workspace roster and the pending invite list — invite people, change roles, suspend, remove, and do any of those to many people at once.
- [Workload](https://projectri.com/docs/admin/workload.md): Who is carrying what and who has room — open tasks, overdue work and logged hours against each person's weekly capacity, with the capacity and skills editable in place.
- [Team](https://projectri.com/docs/workspace/team.md): The workspace roster, the org chart with reporting lines, and a live activity timeline — with each person's department, branch, job role, workload and skills.