Skip to main content

🔐 Roles

Overview​

We expose a small set of roles to cover administration and testing workflows. Use these roles to grant the least privilege required for a user to do their job.

The roles introduced here are:

  • admin
  • dq admin
  • tester
  • dq tester

Role definitions​

  • admin

    • Full application access. This role can view and modify everything in the application, including global Settings and all Connections.
    • Abilities: manage users and roles, configure application-wide settings, create/update/delete connections
    • Intended for system owners and platform operators.

  • dq admin

    • Data-quality (DQ) focused administrator. Full access to DQ functionality and DQ-related configuration.
    • Can create and edit DQ checks, DQ pipelines, and DQ-specific connections and settings.

  • tester

    • Limited testing role. Can view existing Connections and clone an existing Connection to create a test copy.
    • Can run tests and view test results, but cannot change global Settings or create new connections from scratch (only cloning an existing connection is allowed by this role).
    • Intended for QA/test engineers who need to reproduce and run tests against existing configurations without changing core settings.

  • dq tester

    • DQ-focused tester. Can view and clone DQ-related Connections and run DQ checks and view their results.
    • Does not have permissions to modify global Settings or manage users/roles.

Permissions summary​

  • admin: full access (Settings, Connections, Users, Roles, all data and actions).
  • dq admin: full access within the DQ area and DQ resources;
  • tester: read access to connections, ability to clone existing connections, run tests, view results; no settings or user/role management.
  • dq tester: same as tester but scoped to DQ resources and DQ checks.