Home
Personnel

What Are Teams and How Do I Manage Them in the Dusk FSM?

## What Are Teams and How Do I Manage Them in Dusk FSM?

Teams in **Dusk FSM** let you organise Staff into groups and control visibility using **One-to-Many (1:M)** or **Many-to-Many (M:M)** structures.

Each Team can have one or more **Team Managers**, identified by a crown icon, who can see the Staff assigned to that Team.

Teams are useful when you need to manage Staff visibility, approvals and access based on how your organisation is structured, such as depot, region or business unit.

Teams also support **Role-based permissions**, allowing you to assign default Roles to a Team and override those Roles for individual Team members when required.

---

## When to use Teams

Teams are a good fit when you want:

* One Manager to have visibility of multiple Staff members.
* Multiple Managers to share visibility of the same Staff members.
* Separate groups such as field Teams and office Teams.
* Alignment with your organisational structure, such as states, divisions or locations.
* A scalable way to group Staff for approvals, scheduling and Work assignment.
* Consistent permissions for Staff within the same Team.
* Flexibility to assign different Roles to individual Team members.

Teams provide a flexible way to manage Staff visibility and permissions without configuring every Staff member individually.

---

## Create and manage a Team

1. Go to **Personnel → Staff → Teams**.
2. Select **Team** to create a new Team.
3. Enter a Team name.
4. Add Staff members to the Team.
5. Assign one or more Managers using the **crown icon**.
6. Configure Team Roles or individual member Roles where required.
7. Select **Save**.

Once saved, Team Managers have visibility of the Staff assigned to their Team for supported operational workflows.

![Dusk FSM Teams Roles](https://help.duskmobile.com/uploads/markdown/20261019-171728-502.png "Dusk FSM Teams Roles")

---

## Team visibility: One-to-Many and Many-to-Many

Dusk FSM supports both **One-to-Many (1:M)** and **Many-to-Many (M:M)** Team visibility.

This allows organisations to configure who can see Staff members without creating separate Staff records or duplicating Teams.

| Visibility structure | Description | Example |
| --- | --- | --- |
| **1:M — One-to-Many** | One Team Manager can see multiple Staff members assigned to a Team. | A Regional Manager with visibility of 10 field technicians. |
| **M:M — Many-to-Many** | Multiple Team Managers can see the same Staff members assigned to a Team. | An Operations Manager and Service Manager both having visibility of the same field technicians. |

### How Team visibility works

* **Managers can see all Staff assigned to their Team.**
* Multiple Managers assigned to the same Team share visibility of its Staff members.
* Staff members do not automatically gain visibility of other Team members simply because they belong to the same Team.
* A Manager can also be included as a Staff member within the same Team.
* A Staff member can belong to multiple Teams, making them visible to the Managers of each Team.

### Example: Multiple Managers sharing Team visibility

A Field Operations Team contains 12 field technicians.

The organisation assigns both the Operations Manager and Service Manager as Team Managers.

Both Managers can see the same 12 technicians through their shared Team.

This provides **Many-to-Many (M:M) visibility** without requiring duplicate Teams or Staff records.

> **Tip:** If everyone in a Team needs visibility of everyone else, add each person to both the **Manager** and **Staff** lists.

**Important: Everyone seeing everyone**

If you want **every person in a Team to see every other person**, each person must be assigned as **both a Manager and a Staff member** within that Team.

Being a Staff member alone does not provide visibility of other Team members. Being a Manager provides visibility of Staff members, but each person must also be included in the Staff list to be visible to the other Managers.

---

## Understanding Team Roles and permissions

Teams can have default Roles that determine the permissions inherited by their members.

When a Staff member belongs to a Team, they receive the permissions associated with that Team's default Roles unless different Roles have been assigned specifically to them within that Team.

### Team default Roles

Team default Roles provide a consistent set of permissions for Team members.

For example, an Operations Team may have a default Role that allows its members to view and manage operational records.

New members automatically inherit the Team's default permissions unless a member-specific Role override is configured.

### Member-specific Role overrides

Dusk FSM allows you to assign different Roles to an individual Staff member within a Team.

This is useful when a Team member requires different permissions from the rest of the Team.

To configure an override:

1. Open **Personnel → Staff → Teams**.
2. Select the Team you want to manage.
3. Locate the Staff member in the Team membership list.
4. Use the **Roles** field on their row to select one or more Roles.
5. Select **Save**.

**How the override works:**

* The selected Roles **replace that Team's default Roles** for the individual member.
* Other members continue to inherit the Team's default Roles.
* Multiple Roles can be selected, and their permissions are combined.
* The override applies only to that Team.
* Roles assigned directly to the Staff member or inherited through other Teams remain unchanged.

If the member's Roles field is left empty, they continue to inherit the Team's default Roles.

> **Important:** A member-specific Role override only replaces the default Roles of that particular Team. It does not remove permissions granted through other Teams or individual Staff Roles.

---

## Managing Staff across multiple Teams

A Staff member can belong to more than one Team.

This is useful when Staff work across multiple regions, departments or operational groups.

For example, someone working across two regions may belong to both the Northern Operations Team and Southern Operations Team.

The Managers of both Teams have visibility of that Staff member.

### How permissions work across multiple Teams

Dusk FSM combines permissions from:

* Roles assigned directly to the Staff member.
* Default or member-specific Roles from their first Team.
* Default or member-specific Roles from any additional Teams.

This is known as the Staff member's **effective permissions**.

### Example: Staff with multiple Team memberships

A Staff member belongs to two Teams:

| Team | Role configuration | Permissions |
| --- | --- | --- |
| Northern Operations | Default Operations Role | View and manage operational records |
| Southern Operations | Member-specific Viewer Role | View permitted records |

The Staff member receives the combined permissions from both Teams, along with any individual Roles assigned to their Staff profile.

Changing the member's Role in the Southern Operations Team does not remove permissions inherited from the Northern Operations Team.

**Team visibility and Role permissions serve different purposes:** Team Managers gain visibility of Staff assigned to their Teams, while Roles determine the actions and functionality available to individual users.

---

## Administrator access through Teams

Administrator permissions can also be inherited through Team membership.

For example, the **Default** and **Administrator** Teams can provide the Administrator Role to their members.

If a Staff member inherits Administrator access from a Team, assigning a more restrictive Role directly to their Staff profile will not remove that access.

To change the permissions inherited from a particular Team, configure a member-specific Role override on their Team membership row.

**Remember:** If the Staff member also receives Administrator access through another Team or an individual Role, they will retain that access.

When restricting permissions, review all Team memberships and individual Roles.

For more information about how permissions are combined, see [How Do Roles Work in Dusk FSM](https://help.duskmobile.com/article/Personnel/How-Do-Roles-Work-in-Dusk-FSM).

---

## Key notes

* Teams support **1:M and M:M Staff visibility**.
* A Team can have more than one Manager.
* Multiple Managers can share visibility of the same Team members.
* Staff do not automatically gain visibility of other Team members.
* A Staff member can belong to multiple Teams.
* Managers of different Teams can have visibility of the same Staff member.
* Teams support operational workflows such as Work assignment, approvals and Staff scheduling.
* Teams can have default Roles that members inherit.
* Member-specific Roles replace that Team's default Roles for the individual member.
* Multiple Roles can be assigned to a Team member.
* Permissions from individual Roles and multiple Teams are combined.
* Changing one Team's Roles does not remove permissions granted elsewhere.
* Existing Team permissions remain unchanged unless member-specific Roles are configured.

---

## Frequently Asked Questions

### Why can't I see Staff in my Team?

First, check that you are assigned as a **Manager** of the Team.

A Team can have multiple Managers, and a Manager can also be included as a Staff member in the same Team.

Only Managers can view all Staff assigned to their Team. If you want everyone in the Team to be able to see each other, add each person to both the **Manager** and **Staff** lists.

### Can a Team have multiple Managers?

Yes. Dusk FSM supports Many-to-Many (M:M) visibility, allowing multiple Managers to see the same Staff members.

### What is the difference between 1:M and M:M Team visibility?

**1:M (One-to-Many)** means one Manager can see multiple Staff members within a Team.

**M:M (Many-to-Many)** means multiple Managers can see the same Staff members within a Team.

### Can a Staff member belong to multiple Teams?

Yes. Staff can belong to multiple Teams, making them visible to the Managers of each Team.

Permissions from each Team are also combined.

### Can all Team members see each other?

Not automatically. Team membership alone does not provide visibility of other Team members.

To allow all members to see each other, assign them to both the Manager and Staff lists within the Team.

### Can I assign different Roles to individual Team members?

Yes. Use the Roles field on the member's Team row to assign one or more Roles.

These replace the Team's default Roles for that member only.

### What happens if I leave a Team member's Roles field empty?

The Staff member inherits the Team's default Roles.

### Do Team Roles override individual Staff Roles?

No. Permissions from Team Roles and individual Staff Roles are combined.

Only the default Roles of a particular Team are replaced when member-specific Roles are configured for that Team membership.

### Why does a Staff member still have access after I change their Team Role?

They may receive the same permissions through another Team or a Role assigned directly to their Staff profile.

Review all their Role assignments and Team memberships to identify the source of access.

### Do I need to update my existing Teams?

No. Existing Teams continue to use their default Roles unless you configure member-specific Roles for individual members.

---

## Related Articles

* [How Do Roles Work in Dusk FSM](https://help.duskmobile.com/article/Personnel/How-Do-Roles-Work-in-Dusk-FSM)
* [What Are Crews and How Do I Manage Crews in the Dusk FSM](https://help.duskmobile.com/article/Personnel/What-are-Crews-and-how-do-I-manage-Crews-in-Dusk-FSM)
* [How Do I Add Staff in the Dusk FSM](https://help.duskmobile.com/article/Personnel/How-Do-I-Add-Staff-in-the-Dusk-FSM)
* [How Do the Staff Business Rules Work in Dusk FSM](https://help.duskmobile.com/article/Personnel/How-Do-the-Staff-Business-Rules-Work-in-Dusk-FSM)
* [How Does the Shift Functionality Work in the Dusk FSM](https://help.duskmobile.com/article/Personnel/How-does-the-Shift-functionality-work-in-the-Dusk-FSM)

---

Updated on October 20, 2026

What Are Teams and How Do I Manage Them in the Dusk FSM?

Need Support?

Error

Delete Article