User Roles and Access Control (RBAC)

ACCELQ employs a robust Role-Based Access Control (RBAC) system designed to secure test assets and streamline collaboration in enterprise environments. By defining custom roles, organizations can ensure that team members access only the functionalities required for their specific responsibilities.

Roles in ACCELQ are Project-Specific. This means a single user can have full administrative privileges in one project while having restricted "Read-Only" access in another, depending on their assignment.

Governance Hierarchy

Understanding User Roles starts with understanding the two levels of administration in ACCELQ:

Tenant Admin (Platform Governance)

The Tenant Admin is the superuser for the entire organization.

• Role: Defines the standard User Roles available for use across the organization.

• Privilege: Only a Tenant Admin can Create, Edit, or Delete a User Role.

Project Admin (Operational Management)

The Project Admin manages specific projects.

• Role: Assigns the predefined User Roles to team members within their specific project.

• Privilege: Cannot create new Role definitions, but controls who gets which Role.

Anatomy of a User Role

A User Role is a collection of permissions that dictate what a user can view, edit, or delete. When defining a role, permissions are categorized into four logical areas:

Automation Assets

Controls access to the core functional components of test automation: Test Suites, Scenarios, Test Cases, Contexts, and Actions.

For each component, permissions are set as:

• Read Only: User can view the asset but cannot make changes.

• Read-Write: User can create new assets and edit existing ones.

• Delete: User can permanently delete the asset.

  • Note: The "Delete" permission is decoupled from "Read-Write." This allows you to grant Edit access while preventing accidental deletion of critical assets.

Manual Assets

Controls access to Manual Test Cases and Manual Scenarios.

• Read Only: View access to manual test steps.

• Read-Write: User can create new manual test assets and edit existing ones.

• Delete: Authority to permanently delete manual tests.

Data & Resources

Controls access to supporting data structures and the Project Dashboard.

• Data Entities: Permissions for Global Properties, Data Lists, and Run Properties.

• Dashboard:

  • Read-Only: View analytics and charts.

  • Read-Write: Create custom widgets, modify charts, and rearrange the dashboard layout.

  • Delete: Remove widgets from the dashboard.

Other Privileges

These are special, high-level project governance permissions:

• Allow publishing Actions: Authority to publish an Action for cross-project usage (essential for "Center of Excellence" teams).

• Allow purging test results: Authority to bulk-delete execution history in a Project.

• Project merge/update: Authority to perform version control operations (Branching/Merging).

• Allow updating Live releases: Authority to update connected Add-ons (e.g., Salesforce, Oracle) to new versions.

Creating and Managing Roles

Access Required: Tenant Admin

To manage roles, navigate to Tenant Administration > Manage User Roles.

The Role Wizard

Clicking "Add New Role" opens the configuration wizard.

1. Automation Assets: Set granular Read/Write/Delete permissions for core entities.

2. Manual Assets: Configure access for manual testing components.

3. Data & Resources: Define control over global data and dashboard layout.

4. Other Permissions: Toggle specific administrative capabilities.

Enterprise Best Practices

In large organizations, we recommend defining roles based on personas rather than seniority. Here are common examples:

Example Role 1: "Automation Lead"

Designed for senior engineers responsible for architecture and maintenance.

• Automation Assets: Read-Write + Delete (Full control).

• Other Permissions: "Project merge/update" enabled (to manage branching).

• Dashboard: Read-Write (to set up team reporting).

Example Role 2: "Contributor / Automation Engineer"

Designed for team members building daily scripts.

• Automation Assets: Read-Write (Enabled), Delete (Disabled).

  • Rationale: They can build and fix tests, but cannot accidentally delete Actions or core scenarios.

• Other Permissions: "Purging results" disabled.

Example Role 3: "Manual Tester / SME"

Designed for business users who execute tests or review logic.

• Automation Assets: Read-Only.

• Manual Assets: Read-Write.

• Dashboard: Read-Only.

Example Role 4: "Viewer / Stakeholder"

Designed for management needing visibility into quality status.

• All Assets: Read-Only.

• Dashboard: Read-Only.

How to View Your Role

If you are unsure of your access level in a specific project:

1. Log in to ACCELQ and open the project.

2. Click the Project Name in the top navigation bar.

3. Your assigned Role for the current project is displayed in the project info card.