# Team Best Practices

Source: https://userguide.qualytics.io/settings/access/teams/best-practices/

Follow these guidelines to keep your teams well-organized and secure.

## Team Organization

- Yes Organize teams around functional boundaries (e.g., "Data Engineering", "Data Quality", "Analytics").
- Yes Use descriptive names that clearly indicate the team's purpose and scope.
- Yes When a team's name has to match an identity-provider group, keep the group string as the **Name** and give the team a **Display Name** people can read. [Group sync](https://userguide.qualytics.io/deployments/idp-group-sync/) matches on the Name only.
- Yes Keep team sizes manageable. Smaller, focused teams are easier to audit and maintain.
- No Create teams for individual users. Use team-level access, not user-level.
- No Assign all datastores to the Public team. This defeats the purpose of team-based access control.

## Permission Assignment

- Assign the **least privilege** permission level needed for the team's work
- Use **Viewer** or **Reporter** for teams that only need read access
- Use **Editor** only for teams that need full datastore management capabilities
- Review and update permissions when team responsibilities change

## Public Team Usage

- The Public team is meant for datastores that should be accessible to **everyone** in the organization
- Avoid assigning sensitive datastores to the Public team
- If users need no default access, keep the Public team with no datastores assigned

## Membership Strategy

- Add [Service Users](https://userguide.qualytics.io/settings/access/service-users/introduction/) to teams to scope their access to specific datastores
- Use [Directory Sync](https://userguide.qualytics.io/settings/access/directory-sync/introduction/) with managed or self-hosted deployments to synchronize users, Teams, and Team membership from your identity provider
- For self-hosted deployments that authenticate through an OIDC or SAML identity provider, [just-in-time group sync](https://userguide.qualytics.io/deployments/idp-group-sync/) is an add-only alternative. Removing an IdP group does not revoke Team membership, so pair it with a periodic reconciliation of Team membership against the group listing recorded for each account
- Choose one authoritative Team membership strategy. If both methods are enabled, sign-in mapping can add a membership that Directory Sync previously removed
- For more details on how team membership works with Service Users, see [Team Membership](https://userguide.qualytics.io/settings/access/service-users/deep-dive/how-it-works/#team-membership) on the Service Users page

## Regular Audits

- Periodically review team membership to ensure users still belong to the correct teams
- Remove users from teams when they change roles or responsibilities
- Review which datastores are assigned to each team to avoid unnecessary exposure

---

## See Also

- **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/)
- **Examples**

  Team setups for common goals: least privilege by department, a locked-down Public team, a team filled by an identity-provider group, and more.

  [Examples](https://userguide.qualytics.io/settings/access/teams/examples/)

*Last updated: September 16, 2026.*
