# Team Examples

Source: https://userguide.qualytics.io/settings/access/teams/examples/

Team setups people actually ask for, and the configuration that produces them. The scenarios below follow one fictional company, Acme Retail, as its access needs grow. Each one starts from a situation and ends with the teams to create, the equivalent [Teams API](https://userguide.qualytics.io/settings/access/teams/api/) payload, and what each person can do afterwards. The click-through steps are in [Add a Team](https://userguide.qualytics.io/settings/access/teams/how-tos/add-team/); the permission levels are explained in [Team Permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/).

> **Note: About the payloads**
>
> The payloads use example IDs. In your deployment, take user IDs from the [Personal Account API](https://userguide.qualytics.io/settings/access/users/api/) and datastore IDs from the datastore details page or the Datastores API.

**Tab: Least Privilege by Department**

**The situation:** Acme Retail has one production warehouse. Data engineers run profiles and scans and maintain the checks. Business analysts review checks and anomalies and need to see source records to investigate them, but must not change anything. Everyone else in the company should not see the warehouse at all.

**Team configuration**

| Team | Permission | Users | Source Datastores | Enrichment Destinations |
| --- | --- | --- | --- | --- |
| `Data Engineering` | **Editor** | The four data engineers | `Retail Warehouse` | `Quality Enrichment` |
| `Business Analytics` | **Viewer** | The analysts | `Retail Warehouse` | None |
| `Public` | **Reporter** | Everyone, automatically | None | None |

**API payload** for the analysts' team:

```json
{
  "name": "Business Analytics",
  "description": "Analysts who review checks and anomalies on the retail warehouse",
  "permission": "Viewer",
  "user_ids": [12, 15, 18, 21],
  "datastore_ids": [10]
}
```

**What each person can do**

| Person | On `Retail Warehouse` |
| --- | --- |
| A data engineer | Runs operations, creates and edits checks, resolves anomalies, and manages the enrichment datastore. |
| An analyst | Opens the datastore, reads every check and anomaly, views source records. Cannot run operations or edit checks. |
| Anyone else | Does not see the datastore. The Public team has nothing assigned, so it grants nothing. |

**Result:** Each department has exactly the level its work needs, and the warehouse is invisible to people outside those two teams.

**Tab: Locked-Down Public Team**

**The situation:** Acme Retail is about to connect its identity provider, so dozens of accounts will be created on first sign-in. Security wants new accounts to see no data until an Admin, or group sync, places them on a team.

**Team configuration**

| Team | Permission | Users | Source Datastores | Enrichment Destinations |
| --- | --- | --- | --- | --- |
| `Public` | **Reporter** | Everyone, automatically | None | None |

Open the **Public** team with [Edit a Team](https://userguide.qualytics.io/settings/access/teams/how-tos/edit-team/) and clear both datastore fields. Its permission level then makes no difference, because there is nothing for it to apply to. The Public team's Name and users cannot be changed, and it cannot be deleted.

**API payload** (the Public team always has ID `-1`; only its permission and datastores are accepted):

```json
{
  "name": "Public",
  "permission": "Reporter",
  "datastore_ids": []
}
```

**Result:** A person who signs in for the first time can open the platform and sees no datastores. Access begins when an Admin adds them to a team, or when [group sync](https://userguide.qualytics.io/deployments/idp-group-sync/) does it at their next sign-in.

> **Warning: Managers still need Editor somewhere**
>
> Creating a datastore requires the **Manager** role plus the **Editor** team permission on one of the new datastore's teams. With the Public team locked down, every Manager who creates datastores must belong to a team with Editor. See [Why can't a Manager create a datastore?](https://userguide.qualytics.io/settings/access/teams/faq/#why-cant-a-manager-create-a-datastore).

**Tab: Team Filled by an Identity-Provider Group**

**The situation:** Acme Retail's directory has a security group called `ACME-DQ-PROD-ANALYSTS-RW`. Membership of that group is what should decide who can author checks on the production warehouse, and nobody at Acme wants to read that string inside Qualytics.

**Team configuration**

| Field | Value |
| --- | --- |
| **Name** | `ACME-DQ-PROD-ANALYSTS-RW` |
| **Display Name** | `Production Analysts` |
| **Permission** | **Author** |
| **Users** | Leave empty; group sync fills it |
| **Source Datastores** | `Retail Warehouse` |

**API payload**

```json
{
  "name": "ACME-DQ-PROD-ANALYSTS-RW",
  "display_name": "Production Analysts",
  "description": "Filled by the ACME-DQ-PROD-ANALYSTS-RW directory group",
  "permission": "Author",
  "datastore_ids": [10]
}
```

**Result:** With **Sync groups to Teams** turned on for the sign-in provider, every person who carries that group is added to the team at their next sign-in, because the match uses the **Name**. Everywhere the team appears, people see **Production Analysts**; hovering over it in the Teams list shows the Name underneath. Removing someone from the directory group does not remove them from the team, so plan the reconciliation routine described in [Just-in-Time Provisioning and Group Sync](https://userguide.qualytics.io/deployments/idp-group-sync/).

> **Tip: Do not rename the team to make it friendlier**
>
> Changing the Name breaks the match silently. Change the Display Name instead. See [Name and Display Name](https://userguide.qualytics.io/settings/access/teams/how-it-works/#name-and-display-name).

**Tab: Drafters and Authors on One Datastore**

**The situation:** Acme Retail's finance team has two junior analysts who know the data well and should propose checks, and a data steward who decides which checks go live. Proposals must never run against the ledger until the steward approves them.

**Team configuration**

| Team | Permission | Users | Source Datastores |
| --- | --- | --- | --- |
| `Finance Contributors` | **Drafter** | The two junior analysts | `Finance Ledger` |
| `Finance Stewards` | **Author** | The data steward | `Finance Ledger` |

**API payload** for the contributors:

```json
{
  "name": "Finance Contributors",
  "description": "Proposes checks on the finance ledger as drafts",
  "permission": "Drafter",
  "user_ids": [31, 32],
  "datastore_ids": [22]
}
```

**What each person can do**

| Person | On `Finance Ledger` |
| --- | --- |
| A junior analyst | Creates checks as drafts and edits their own drafts. Cannot activate a check or run operations. |
| The steward | Activates, edits, and archives checks, and manages anomalies. |

**Result:** The review step lives in the permission model itself. Nothing a Drafter creates affects the ledger until an Author activates it. See [Drafter](https://userguide.qualytics.io/settings/access/teams/team-permissions/drafter/) and [Author](https://userguide.qualytics.io/settings/access/teams/team-permissions/author/).

**Tab: Two Teams, Two Levels, One Person**

**The situation:** Acme Retail's head of finance sits on the stakeholders team that reads the ledger. The head also leads the data quality effort on it and needs to author checks. Adding them to a second team should raise their access, and adding them to the read-only team should never lower it.

**Team configuration**

| Team | Permission | Users | Source Datastores |
| --- | --- | --- | --- |
| `Finance Stakeholders` | **Viewer** | Finance leadership, including the head of finance | `Finance Ledger` |
| `Finance Stewards` | **Author** | The data steward and the head of finance | `Finance Ledger` |

**Result:** The head of finance gets **Author** on `Finance Ledger`, because the highest permission among a person's teams applies to each datastore. The other stakeholders stay at **Viewer**. Adding someone to a lower team never reduces what a higher team already grants, so teams can overlap freely.

**Tab: Scoped Service User for a Pipeline**

**The situation:** Acme Retail's orchestration tool must trigger scans on the orders lakehouse after each nightly load, and the security team wants that automation to reach nothing else.

**Team configuration**

| Team | Permission | Users | Source Datastores |
| --- | --- | --- | --- |
| `Pipeline Automation` | **Editor** | The [Service User](https://userguide.qualytics.io/settings/access/service-users/introduction/) `svc_orchestrator` | `Orders Lakehouse` |

**API payload**

```json
{
  "name": "Pipeline Automation",
  "description": "Service account that triggers scans on the orders lakehouse",
  "permission": "Editor",
  "user_ids": [204],
  "datastore_ids": [35]
}
```

**Result:** The Service User can trigger operations and manage checks on `Orders Lakehouse` and reaches no other datastore, apart from whatever the Public team grants. Give it the **Member** role and keep it off every other team. If a second pipeline needs a different datastore, create a second team rather than widening this one. See [Team Membership](https://userguide.qualytics.io/settings/access/service-users/deep-dive/how-it-works/#team-membership) on the Service Users page.

**Tab: Reporters for Compliance**

**The situation:** Acme Retail's compliance officers must see data quality results across every datastore for their audits, but they should never open source records or touch a check.

**Team configuration**

| Team | Permission | Users | Source Datastores |
| --- | --- | --- | --- |
| `Compliance` | **Reporter** | The compliance officers | Every source datastore |

**API payload**

```json
{
  "name": "Compliance",
  "description": "Read-only reporting access across all datastores for audits",
  "permission": "Reporter",
  "user_ids": [41, 42],
  "datastore_ids": [10, 22, 35, 48]
}
```

**Result:** The officers can open every datastore's reports, scores, checks, and anomaly lists, but source records stay hidden from them, which is the difference between Reporter and Viewer. When a new datastore is created, add it to the `Compliance` team so the audit view stays complete. See [Reporter](https://userguide.qualytics.io/settings/access/teams/team-permissions/reporter/).

**Tab: Temporary Team for a Contractor**

**The situation:** Acme Retail hires a consultancy for a three-month migration of the marketing warehouse. The consultants need full control of that one datastore and must lose it the day the engagement ends.

**Team configuration**

| Team | Permission | Users | Source Datastores | Enrichment Destinations |
| --- | --- | --- | --- | --- |
| `Marketing Migration (Q4)` | **Editor** | The consultants' accounts | `Marketing Warehouse` | `Quality Enrichment` |

**API payload**

```json
{
  "name": "Marketing Migration (Q4)",
  "description": "Consultancy engagement, ends 31 December",
  "permission": "Editor",
  "user_ids": [301, 302, 303],
  "datastore_ids": [48, 20]
}
```

**Result:** During the engagement the consultants work on the marketing warehouse like any engineer. When it ends, an Admin [deletes the team](https://userguide.qualytics.io/settings/access/teams/how-tos/delete-team/): every consultant loses the access granted through it at once, while their accounts and any other memberships are untouched. Because `Marketing Warehouse` also belongs to `Data Engineering`, the deletion is not blocked; a datastore that belonged only to this team would have to be assigned elsewhere first. [Deactivate](https://userguide.qualytics.io/settings/access/users/how-tos/deactivate-user/) the consultants' accounts as well if they should not sign in again.

---

## See Also

- **Best Practices**

  Team organization, permission assignment, Public team usage, and regular audits.

  [Best Practices](https://userguide.qualytics.io/settings/access/teams/best-practices/)
- **Permissions**

  User roles required to view, create, edit, and delete teams.

  [Permissions](https://userguide.qualytics.io/settings/access/teams/permissions/)
- **How It Works**

  Permission matrix, team roles (Editor, Author, Drafter, Viewer, Reporter), the Teams list, and detailed capability tables.

  [How It Works](https://userguide.qualytics.io/settings/access/teams/how-it-works/)

*Last updated: September 19, 2026.*
