> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fentufsm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dynamic Teams

> Automatic team membership based on rules and criteria

<img src="https://mintcdn.com/fentu/hwQj1zN52k4D8yBe/images/fentu-fsm/workforce/dynamic-teams-list.png?fit=max&auto=format&n=hwQj1zN52k4D8yBe&q=85&s=888a554a36deb31aec0b2af5ba1a7d2d" alt="Dynamic Teams List View" width="1280" height="720" data-path="images/fentu-fsm/workforce/dynamic-teams-list.png" />

## Overview

Dynamic Teams automatically determine membership based on rules and criteria you define. Unlike static teams where you manually add members, dynamic teams automatically include technicians who match specified conditions.

<Note>
  Dynamic teams are powerful for creating groups that automatically update as technician attributes change. When a technician gains a new skill or changes location, they're automatically included or excluded from relevant dynamic teams.
</Note>

## When to Use Dynamic Teams

Create dynamic teams for:

* **Skill-Based Groups** - All technicians with specific certifications
* **Location-Based Groups** - Technicians within a geographic area
* **Availability Groups** - Technicians currently on duty
* **Experience-Based Groups** - Senior technicians or apprentices
* **Combined Criteria** - Complex conditions using multiple attributes

<Tip>
  Use dynamic teams when membership should change automatically based on data. Use static teams when you want direct control over membership.
</Tip>

***

## Dynamic Team Information

Each dynamic team includes:

| Field               | Description                           |
| ------------------- | ------------------------------------- |
| **Team Name**       | Descriptive name                      |
| **Description**     | Explanation of the team's purpose     |
| **Rules**           | Criteria that determine membership    |
| **Current Members** | Technicians who currently match rules |
| **Status**          | Active or inactive                    |

### Rule Components

Rules can be based on:

| Attribute          | Example Rule                                         |
| ------------------ | ---------------------------------------------------- |
| **Skills**         | Has skill "Machine Installation" with level "Expert" |
| **Certifications** | Has valid EPA 608 certification                      |
| **Location**       | Home address within 20 miles of branch               |
| **Branch**         | Assigned to North Branch                             |
| **Status**         | Is currently Active                                  |
| **Experience**     | Start date before 2020                               |
| **Team**           | Member of Service Team                               |

***

## Creating Dynamic Teams

<Steps>
  <Step title="Navigate to Dynamic Teams">
    Go to Workforce > Dynamic Teams
  </Step>

  <Step title="Click Create">
    Start a new dynamic team
  </Step>

  <Step title="Enter Team Details">
    Provide name and description
  </Step>

  <Step title="Define Rules">
    Create rules that determine membership
  </Step>

  <Step title="Set Rule Logic">
    Choose AND/OR combinations for multiple rules
  </Step>

  <Step title="Preview Members">
    Review who currently matches the rules
  </Step>

  <Step title="Save Team">
    Activate the dynamic team
  </Step>
</Steps>

### Building Rules

<Steps>
  <Step title="Select Attribute">
    Choose what to evaluate (skill, location, etc.)
  </Step>

  <Step title="Choose Operator">
    Select comparison type (equals, contains, greater than)
  </Step>

  <Step title="Set Value">
    Define the value to match
  </Step>

  <Step title="Add More Rules">
    Optionally add additional conditions
  </Step>

  <Step title="Set Logic">
    Choose whether ALL rules must match (AND) or ANY rule (OR)
  </Step>
</Steps>

<Warning>
  Test your rules before activating. Preview the resulting membership to ensure the rules capture the intended technicians.
</Warning>

***

## Rule Logic

### AND Logic

ALL conditions must be true:

```
Has skill "Machine"
AND Has skill "Refrigeration"
AND Status is Active
```

Result: Only technicians with both skills who are active

### OR Logic

ANY condition can be true:

```
Has skill "Machine Installation"
OR Has skill "Machine Repair"
```

Result: Technicians with either (or both) skills

### Combined Logic

Complex rules combine AND and OR:

```
(Has skill "Electrical" OR Has skill "Machine")
AND Status is Active
AND Branch is "North"
```

<Info>
  Start with simple rules and add complexity as needed. Complex rules are harder to troubleshoot when membership doesn't match expectations.
</Info>

***

## Dynamic Team Examples

### Certification-Based Team

**Emergency Response Team**

* Has certification "Emergency Response"
* Certification is not expired
* Status is Active

### Skill-Level Team

**Senior Technicians**

* Start date before 2020
* Has skill level "Expert" in at least one skill
* Status is Active

### Geographic Team

**Downtown Coverage**

* Home address within 10 miles of downtown office
* OR Assigned to Downtown branch

### Combined Team

**Machine Emergency Response**

* Has skill "Machine"
* Has certification "EPA 608" (not expired)
* Currently on duty
* Status is Active

***

## Managing Dynamic Teams

### Monitoring Membership

Dynamic teams update automatically, but you should:

* Periodically review current membership
* Check that expected technicians are included
* Verify no one is incorrectly excluded
* Adjust rules if results don't match intent

### Troubleshooting

When membership isn't as expected:

1. Check technician attributes match rule criteria
2. Verify rule logic (AND vs OR)
3. Look for typos in rule values
4. Check if attributes have been updated
5. Review certification expiration dates

### Rule Maintenance

Keep rules current:

* Update when skill names change
* Adjust geographic boundaries as territory changes
* Modify certification requirements as regulations change
* Remove obsolete criteria

***

## Best Practices

<AccordionGroup>
  <Accordion title="Clear Naming" icon="tag">
    Name dynamic teams descriptively. The name should indicate what criteria defines membership.
  </Accordion>

  <Accordion title="Document Rules" icon="file-alt">
    Add descriptions explaining why rules are configured as they are. Future administrators will thank you.
  </Accordion>

  <Accordion title="Start Simple" icon="compress">
    Begin with straightforward rules. Add complexity only when needed.
  </Accordion>

  <Accordion title="Regular Audits" icon="search">
    Periodically review dynamic team membership. Ensure rules still align with business needs.
  </Accordion>

  <Accordion title="Test Changes" icon="vial">
    Preview membership changes before saving rule modifications. Unexpected changes can affect dispatch.
  </Accordion>

  <Accordion title="Combine with Static" icon="layer-group">
    Use dynamic teams for automatic membership and static teams for manual overrides when needed.
  </Accordion>
</AccordionGroup>

***

## Common Questions

<AccordionGroup>
  <Accordion title="How often do dynamic teams update?" icon="question">
    Dynamic team membership is evaluated when needed (e.g., at dispatch time). Changes to technician attributes are reflected immediately.
  </Accordion>

  <Accordion title="Can I manually add someone to a dynamic team?" icon="question">
    No, dynamic team membership is automatic. If you need to include someone who doesn't match rules, adjust the rules or use a static team.
  </Accordion>

  <Accordion title="What if a technician matches multiple dynamic teams?" icon="question">
    A technician can be in multiple dynamic teams simultaneously if they match the criteria for each.
  </Accordion>

  <Accordion title="How do I exclude specific technicians?" icon="question">
    Add exclusion rules (e.g., "Employee ID is not 12345") or use a static team for direct control.
  </Accordion>

  <Accordion title="Can I base rules on work order history?" icon="question">
    Rules are typically based on technician attributes, not history. For history-based assignment, use dispatch rules instead.
  </Accordion>

  <Accordion title="What happens if rules match zero technicians?" icon="question">
    The team will have no members. Work assigned to an empty dynamic team cannot be dispatched until someone matches.
  </Accordion>
</AccordionGroup>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Teams" icon="users" href="/workforce/teams/teams">
    Static team management
  </Card>

  <Card title="Skills" icon="star" href="/workforce/teams/skills">
    Skill definitions
  </Card>

  <Card title="Technicians" icon="user-gear" href="/workforce/technicians/technician-management">
    Technician attributes
  </Card>

  <Card title="Dispatcher" icon="paper-plane" href="/service-apps/dispatcher">
    Dispatch and assignment
  </Card>
</CardGroup>
