How Teams Work
This page explains how teams work in Qualytics — the permission model, how access is granted, and how team membership controls what users can do.
How Team Access Works
When a team is created, it is assigned a permission level and one or more datastores. All members of the team inherit that permission level for all datastores assigned to the team.
- An Admin creates a team and assigns a permission level (e.g., Editor)
- The Admin assigns datastores to the team
- The Admin adds users to the team
- All team members can now access those datastores at the assigned permission level
Note
If a user belongs to multiple teams with different permission levels for the same datastore, the highest permission level applies.
Permission Levels
There are five permission levels, organized from most to least privileged:
| Level | Permission | Purpose | Typical User |
|---|---|---|---|
| 5 | Editor | Full datastore management | Data Engineers, Platform Operators |
| 4 | Author | Quality check lifecycle management | Data Quality Analysts, Data Stewards |
| 3 | Drafter | Check creation (draft only) | Junior Analysts, Contributors |
| 2 | Viewer | Read access with source records | Business Analysts, Stakeholders |
| 1 | Reporter | Report and dashboard access | Executives, Compliance Officers |
Info
For the full permission matrix and detailed capability tables, see the Team Permissions page.
The Public Team
Every user is automatically a member of the Public team. The Public team:
- Cannot be deleted or renamed
- Cannot have its members modified (all users are always included)
- Provides access to all datastores assigned to it
Tip
If users should have no default access, keep the Public team with no datastores assigned. Only assign datastores to specific teams where access is needed.
Team Membership for Service Users
Service Users can also be assigned to teams to scope their API access to specific datastores. This is the recommended way to control what automated integrations can access.
Info
For more details on how team membership works with Service Users, see the Membership Strategy documentation.