Security and Privacy

Workspace access

Your Workspace keeps its Projects, Tests, Runs, and evidence separate from other Workspaces. Only authorized members can access its content.

Review membership regularly and remove people who no longer need access.

Least-privilege test accounts

Use dedicated test accounts with only the permissions required for each journey. Never place passwords, tokens, or recovery codes in Test steps, screenshots, files, or notes.

Controlled environments

Configure approved environments within the appropriate Project. This helps prevent a Test from running against the wrong product or release stage.

Private evidence

When Run evidence becomes available, only authorized Workspace members may access it. Avoid real customer data in fixtures, and redact sensitive information before sharing a bug report outside your team.