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

# Groups

> Configure which source groups sync, how names match, and whether removed groups are deleted.

Groups creates and maintains source organization units as Mitti groups. Employment Hero uses teams, Tanda uses Departments, and Deputy uses Operational Units.

## Shared Settings

These rules apply to Employment Hero teams, Tanda Departments, and Deputy Operational Units. In the integration panel, open **Groups**, **Departments**, or **Operational Units**, respectively.

### Include Patterns

**Default:** Empty, which includes every non-excluded source group.

Use this when only part of your source organization should have groups in Mitti. Add one or more name patterns; a group must match a pattern to be included. This filters by the group name, not by individual employee names.

For example, ` - SC` with **Match mode** set to **Suffix** includes `Warehouse - SC` but not `Social Club`. Exclusions still take precedence.

### Match Mode

**Default:** Contains. This control appears after you add an include pattern.

* **Contains:** The pattern can appear anywhere in the name.
* **Prefix:** The name must start with the pattern.
* **Suffix:** The name must end with the pattern.

Matching ignores letter case. Choose the mode that reflects your naming convention; a short Contains pattern may include more groups than intended.

### Skip Deletion

**Default:** Off.

* **Off:** A previously mapped Mitti group can be deleted when its source disappears or no longer passes the configured filters.
* **On:** Keep that Mitti group instead of deleting it.

Turn this on when groups should be retained in Mitti after the source stops managing them. It does not make an excluded group eligible again or independently protect each user's group membership.

<Warning>
  Changing an include pattern can cause deletion, not just stop future updates. With **Skip deletion**
  off, narrowing include patterns or Tanda team-group rules can delete a mapped Mitti group even
  when the source group still exists. Review existing groups before saving.
</Warning>

## Shared Onboarding Settings

These controls define the two destination group names. To place future starters into those groups by date, also configure [Staged Provisioning in Users](/docs/configuration/users#staged-provisioning).

### Dual-Group Mode

**Default:** Off.

Turn this on when each eligible source group needs both an onboarding group and a regular working group in Mitti. With it off, the sync uses one group per source group. With it on, a source team such as `Warehouse` can produce `Warehouse` and `Onboarding: Warehouse`.

### Strip Pattern

**Default:** Empty. Available only with Dual-Group Mode on.

Enter a suffix to remove from both destination names. Use it to keep a source-only marker out of Mitti: `Warehouse - SC` with strip pattern ` - SC` becomes `Warehouse`. This changes how the name is derived; it does not choose which source groups are included.

### Onboarding Prefix

**Default:** `Onboarding: ` when no prefix is supplied. Available only with Dual-Group Mode on.

Use this to make onboarding groups recognizable in Mitti. For example, prefix `New Starter: ` produces `New Starter: Warehouse`; the regular group remains `Warehouse`.

## Tanda Only

These controls filter the **Team Group** value attached to a Tanda Department. They do not apply to Employment Hero or Deputy.

### Team Group Allowlist

**Default:** Empty, which permits any Team Group value.

Use this when Departments are organized into categories and only selected categories should sync. For example, allow `Operations` to include Departments in that Team Group. A Department must also pass any Include Patterns rules.

### Require Team Group

**Default:** Off.

Turn this on to skip Departments whose Team Group is blank, even with an empty allowlist. Leave it off if uncategorized Departments should remain eligible, subject to the other filters.

With an allowlist configured, a blank or unlisted Team Group does not pass that allowlist regardless of this switch.

## Representative Configuration

Suppose a synthetic Employment Hero organization has `Operations - SC`, `Warehouse - SC`, and `Social Club` teams. The intended Mitti groups are `Operations`, `Warehouse`, and their onboarding variants.

| Setting           | Value          |
| ----------------- | -------------- |
| Include patterns  | ` - SC`        |
| Match mode        | Suffix         |
| Dual-group mode   | On             |
| Strip pattern     | ` - SC`        |
| Onboarding prefix | `Onboarding: ` |
| Skip deletion     | Off            |

This includes only the first two teams, derives clean business-as-usual names, and creates two Mitti groups for each. `Social Club` is not processed.

Review affected existing groups and test the intended naming rule with synthetic examples before saving. A broader pattern can include unintended groups; a narrower pattern can make existing groups eligible for deletion when Skip Deletion is off.

## Dependencies

**Group Memberships** depends on Groups. Groups also interact with:

* **Users > Require group membership**, which provisions only users belonging to at least one synced group;
* **Users > Staged provisioning**, which requires dual-group mode; and
* exclusion groups, which take precedence over normal group processing.

Workforce-access integrations cannot also use team filters or staged provisioning. Bravas configures that policy and will advise which model applies.