Skip to content

Teams

Teams are the primary mechanism for controlling access to datastores and their associated data assets in Qualytics. By organizing users into teams and assigning datastores to those teams, administrators can ensure that users only access the data they need.

What Are Teams?

Teams group users together and define what datastores they can access and at what permission level. Each team has a set of permissions (Editor, Author, Drafter, Viewer, Reporter) that apply to all datastores assigned to that team.

Key Characteristics

  • Datastore-level access: Team permissions control which datastores and data assets (tables, fields, checks, anomalies) a user can interact with
  • Permission inheritance: All members of a team inherit the team's permission level for its assigned datastores
  • Multiple teams: Users can belong to multiple teams, each granting access to different datastores
  • Public team: Every user is automatically part of the Public team, which provides access to all public datastores
  • Admin override: Administrators are not subject to team permissions and can access all data assets

Note

Permissions are assigned to Teams rather than directly to users. Users inherit the permissions of the teams to which they are assigned.

Teams vs User Roles

Teams and user roles serve different purposes:

Aspect User Roles Team Permissions
Scope Platform-level (global) Datastore-level (scoped)
Controls What features/actions a user can perform Which datastores/data a user can access
Assigned to Individual users Groups of users
Examples Admin can manage users; Member can generate tokens Editor can run operations on assigned datastores

Info

For details on user roles (Admin, Manager, Member), see the Personal Accounts documentation.

Deep Dive

Understand how team permissions work — the permission matrix, available roles, and best practices.

  • How It Works

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

    How It Works

  • Best Practices

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

    Best Practices

Managing

Create, view, edit, and delete teams.

  • Add Team

    Create a new team with permissions, users, and datastore assignments.

    Add Team

  • Edit Team

    Update a team's permissions, users, and datastore assignments.

    Edit Team

  • Delete Team

    Permanently remove a team from the system.

    Delete Team

  • Sort Teams

    Organize the teams list by name or created date.

    Sort Teams

  • List Columns

    Understand the Teams list columns: name, description, users, datastores, and created.

    List Columns

More

  • Membership Strategy

    How team membership works with Service Users for scoped automation access.

    Membership Strategy

  • API

    Manage teams programmatically via the Qualytics API.

    API

  • FAQ

    Common questions about teams, permissions, and access control.

    FAQ