Permissions
Actions on a Run (Abort, Resume, Rerun, Delete) are gated by the Editor team permission on the target datastore. Without the right combination of a user role and a team permission on the datastore, the action buttons either do not appear in the expanded Run row or return a permission error when invoked.
Two permission systems
Qualytics has two separate role systems, and a user needs the right combination of both to act on a Run:
- User Roles (Member, Manager, Admin) control what a user can do across the entire workspace.
- Team Permissions (Reporter, Viewer, Drafter, Author, Editor) control what a user can do on specific datastores accessed through team membership.
Team permission matrix
The same team-permission matrix applies to every action on a Run. Whether the action is supported by a specific operation is a separate question (see Action support by operation type below).
| Team permission | Can Abort | Can Resume | Can Rerun | Can Delete |
|---|---|---|---|---|
| Viewer | ||||
| Reporter | ||||
| Drafter | ||||
| Author | ||||
| Editor |
The Editor team permission is granted on a per-datastore basis through team memberships. For a full reference of team permissions and how they are assigned, see Team Permissions Overview.
Admin bypass
Users with the Admin user role bypass all team-permission checks and can act on any Run, regardless of team membership.
Action support by operation type
Permission alone is not enough. The action must also be supported by the operation type. See Available Actions for the full support matrix.
For per-operation permission details (configuring operation settings, scheduling recurring runs, and so on), see the operation's own Permissions page: