Add site logins

To check translations in context, the agent opens your app in each language. If your app needs a sign-in, store a login here. The agent types it in; the AI never sees the password.

1. Open Site logins

Open Work Area › Setup & Control › Site logins.

Choose All pages, then Site logins.

123

123

Manage viewShow Hands-on

123

123

Hands-on viewShow Manage

Swipe the screenshot sideways · tap to enlarge

• 1 Add a test login.
• 2 How a login is picked: by its role. A check that says “log in as admin” uses the login whose role is admin.
• 3 How test data is handled.

2. Add a login

1. Choose Add a test login.
2. Give it a role, such as admin or customer.
3. Type the username and password of a test account.
4. Save it. The list shows the login’s name and role, never the password.

3. How it is kept safe

Promise	What it means
Encrypted at rest	Logins are stored apart from chat and memory
Typed by the browser	The browser running the check types the value; the AI works with the login’s name only
Masked everywhere	Values are hidden in chat, logs, reports and exports
Write-only	Nobody can read a saved password back. Replace or delete it instead.
Audited	Every use is in the audit log, with the run it served

Use test accounts

Screenshots show what your app shows. If your app displays personal data on screen, it is in the evidence. Use test accounts, not real ones.

What’s next

Review and LQAScreenshot checks use these logins.

Test loginsThe same page in a testing project.

Audit logWhere every use is recorded.