AXQA User Management Overview

User Management in AXQA allows administrators to control who can access the workspace, what they can see, and what they can execute. It ensures structured collaboration between internal team members and external clients — while maintaining strict permission boundaries.

As part of the AXQA Execution Intelligence Platform, User Management ensures secure collaboration through structured roles, project-level visibility, and execution-based permission validation.

Why it matters

• Defines clear roles and responsibilities.
• Prevents unauthorized access to projects.
• Protects sensitive execution data.
• Enables controlled client visibility.

Two types of users

Internal Users

Testers, automation engineers, managers, and administrators who actively work inside the platform.

• Create and execute test cases.
• Manage projects and campaigns.
• Access execution history and reports.

Client Users

External stakeholders who require visibility into testing progress without direct modification rights.

• View reports and campaign summaries.
• Monitor release stability.
• Access limited, controlled information.

Permission-based structure

Access in AXQA is never global by default. Permissions are controlled at multiple levels:

• Workspace-level roles.
• Project-level visibility.
• Execution permissions.
• Client-specific dashboard restrictions.

What User Management includes

• Adding and inviting new users.
• Editing roles and permissions.
• Deactivating or removing accounts.
• Managing personal user profiles.
• Configuring client dashboard access.

Designed for control and flexibility

Whether you’re managing a small internal team or working with multiple external clients, User Management gives you the structure to scale safely.

Best practices

• Assign the minimum required permissions per user.
• Review access periodically.
• Separate client users from internal team members.
• Disable accounts that are no longer active.

Security & isolation

• Users only see projects they are assigned to.
• Client dashboards remain isolated per organization.
• Execution permissions are validated server-side.

Related documentation

• Adding & Managing Users
• User Profile Settings
• Client Dashboard Overview
• Security & Execution Permissions