Deactivating or Removing Users in AXQA
When a team member leaves a project or an organization, access must be handled carefully. AXQA allows administrators to either deactivate or permanently remove a user while preserving historical data integrity.
As part of the AXQA Execution Intelligence Platform, user access revocation follows strict permission validation rules. Deactivation or removal never alters historical execution data, ensuring auditability and compliance continuity.
Why it matters
- Prevents unauthorized access after role changes or departures.
- Maintains a clean and accurate user list.
- Protects sensitive project and execution data.
- Preserves historical accountability.
Deactivate vs Remove
Deactivate User
- The account is disabled.
- The user cannot log in.
- All historical activity remains intact.
- Recommended for temporary or internal transitions.
Remove User
- The account is permanently removed from active access.
- The user can no longer authenticate.
- Historical execution records remain preserved.
- Recommended for permanent departures.
Note
AXQA preserves execution accountability even after user removal. Historical test runs remain traceable to the original execution source, supporting governance and regulatory compliance requirements.
What happens to historical data
- All execution history remains unchanged.
- Past actions remain traceable.
- Reports continue to reflect original execution sources.
User removal does not alter previously recorded test results or campaign history.
How it works
- Open User Management.
- Select the user to deactivate or remove.
- Choose the appropriate action.
- Confirm the decision.
- Access is immediately revoked.
When to deactivate
- Temporary leave.
- Internal role reassignment.
- Security review or investigation.
When to remove
- Employee departure.
- End of client engagement.
- Permanent access termination.
Best practices
- Deactivate immediately when access is no longer required.
- Review user list regularly for inactive accounts.
- Prefer deactivation before permanent removal when unsure.
- Ensure project ownership is reassigned before removal.
Common mistakes
❌ Leaving inactive users with access
✔ Disable accounts promptly after departure.
❌ Deleting accounts without considering ownership
✔ Reassign responsibilities before removal.
Security & compliance
- Only administrators can deactivate or remove users.
- Access is revoked immediately upon confirmation.
- Historical execution records remain protected and immutable.
Related documentation
- Adding a New User
- Editing & Updating Users
- User Profile Settings
- Client Dashboard Overview