ACCELQ operates on a secure, two-tiered administrative model designed to support scalability in enterprise environments. This hierarchy ensures that global security settings are centralized, while day-to-day operational control is delegated to specific project owners.
This article explains the distinction between the Tenant Admin (Platform Governance) and the Project Admin (Operational Management).
What is a Tenant?
A Tenant represents your organization’s entire workspace in ACCELQ. It is the container that holds all your:
Projects
Users
Global Roles
Subscription & License Information
Every Tenant is governed by one or more Tenant Admins.
The Tenant Admin (Platform Superuser)
The Tenant Admin is the highest privileged role in ACCELQ. This user controls the "infrastructure" of the testing platform. Their focus is on Governance, Security, and Compliance.
Access: Open ACCELQ. Click on the Profile Icon (top-right corner) > Tenant Administration Portal
You will see the link for Tenant Admin Portal under Profile Icon only if you have Tenant Admin privilege on your instance.
Key Responsibilities:
Project Management: Create new Projects or delete obsolete ones. Create Branch Projects for version control.
User Management: Add users to the platform and manage their subscription status.
Role Definition: Create and configure the User Roles (e.g., defining what an "Automation Lead" is allowed to do).
Security & Compliance: Configure Single Sign-On (SSO), IP Whitelisting, and Password Policies etc.
Branding: Upload the organization's logo and configure email server settings.
Audit: Access the full Audit Log for platform-wide activity.
The Project Admin (Operational Owner)
While the Tenant Admin sets the rules, the Project Admin plays the operational role. They manage the specific settings, integrations, and team members for their assigned project.
Access: Open ACCELQ. Click on the Project Name label in the top-right corner. Click the Settings Icon (Project Administration).
Key Responsibilities:
User Assignment: Add team members to the project and assign them specific Roles (e.g., assigning "John" the "Automation Engineer" role).
Test Management: Configure Status Lists (New/Work In Progress/Under Review etc.) and Execution Parameters.
App Configuration: Manage Application Environments (QA, Staging, Prod) and App Variants (English, French, German etc.).
Integrations: Set up project-specific integrations like Jira, Git (Version Control), or CI/CD pipelines.
Custom Fields: Define custom fields for Test Cases, Scenarios and other assets to fit the team's and application's reporting needs.
Summary of Responsibilities
| Feature | Tenant Admin | Project Admin |
|---|---|---|
| Scope | Entire Organization (Global) | Single Project (Local) |
| Users | Add/Remove Users from Platform | Assign/Remove Users from Project |
| Roles | Define/Edit Roles (Permissions) | Assign Roles to Users |
| Security | SSO, IP Whitelisting, Password Policy | N/A |
| Projects | Create/Delete Projects | Configure Project Settings |
| Integrations | N/A | Setup Defect/Version Control Integrations |
User Roles (RBAC)
While Tenant and Project Admins govern the platform structure, access to specific test assets (like Scenarios, Actions, and Results) in a project is controlled via User Roles.
ACCELQ allows a Tenant Admin to define granular custom roles (e.g., "Automation Lead," "Manual Tester") with specific Read/Write/Delete permissions.
Tenant Admins define these roles.
Project Admins assign these roles to users.
📖 Read the full guide on Creating and Managing User Roles here
Comments
0 comments
Please sign in to leave a comment.