# User Management in AIQ

## Recommended guidance

Use User Management to control who can access AIQ projects, execute tests, manage configuration, and view results. Access should follow least privilege and should be reviewed whenever team membership, responsibilities, or environments change.

## Recommended controls

- Assign roles based on job responsibility, not convenience.
- Use named accounts instead of shared accounts whenever possible.
- Remove or disable accounts for users who no longer need access.
- Review administrators, project owners, and integration/service accounts regularly.
- Protect sensitive projects, credentials, DPLs, repositories, and execution evidence from unnecessary access.

## Operational checklist

1. Confirm the user identity, role, project access, and expected responsibilities.
2. Grant the minimum access required for the task.
3. Document exceptions such as temporary elevated access.
4. Audit inactive users and accounts tied to old integrations.
5. Escalate authentication or SSO issues with timestamps and affected accounts, without sharing passwords.

**Security reminder:** Do not paste passwords into tickets, chat messages, or documentation. Ask users to reset passwords or sign in through the approved login flow.

*Last updated: October 5, 2026*