Adding a New User

Adding a New User in AXQA

Adding a new user in AXQA is a controlled process designed to keep access structured and secure. Administrators can create a user, assign the right role, and define what the user can access from day one.

As part of the AXQA Execution Intelligence Platform, user onboarding follows a structured role-based access control model, ensuring that project visibility and execution rights are explicitly defined from the moment the account is created.

Why it matters

Ensures users only access the projects they need.
Helps teams onboard quickly with clear permissions.
Prevents accidental exposure of sensitive data.
Supports clean separation between internal and client accounts.

When to add a new user

Onboarding a new tester, lead, or manager.
Adding an automation engineer or Smart Agent operator.
Granting a client stakeholder access to dashboards and reports.
Expanding the team during a new project ramp-up.

What you define when creating a user

Basic user identity (name and email).
User type (internal or client).
Role level and permissions.
Project access scope (which projects the user can view or execute in).

Note

AXQA enforces permission validation at execution time, meaning that even newly created users cannot run tests or access data beyond their assigned scope.

How it works

Open User Management from the workspace menu.
Select the option to add a new user.
Enter the user’s basic details (name and email).
Choose the appropriate user type and role.
Assign project access based on what the user needs to work on.
Save the user and confirm activation.

Internal vs client users

Before creating the account, confirm whether the user is internal (execution and management) or client-facing (visibility and reporting).

Internal users – work inside projects, create and execute tests.
Client users – view progress and reports through controlled access.

Note

User access is never global by default — every account operates within defined workspace and project boundaries.

Best practices

Assign the minimum necessary permissions.
Use company emails for long-term access control.
Clearly separate client accounts from internal accounts.
Review project access during onboarding to avoid misconfiguration.

Common mistakes

❌ Granting broad access “just in case”
✔ Start with minimal permissions and expand only when needed.

❌ Mixing client and internal access levels
✔ Use the correct user type to keep visibility controlled.

Security & access

Only authorized administrators can add users.
Project access is enforced at workspace level.
Execution permissions are validated when a user attempts to run tests.

AXQA

Did You Know?