Skip to Content
PersonaMark docs
Personas and goals

Test accounts

Give a goal a login so the agent can sign in, without the username or password ever reaching a model.

Some goals can only be done signed in, like changing a setting or sending an invoice. For those, you save a test account's login with the site, and the goal signs in with it.

Use a test account, never a real one

The agent acts on your live site. Give it an account made for testing, with test data and no power to change anything that matters. A real customer's account, or one that can administer the site, is the wrong choice even with the guardrails in place.

Adding a login

On the project's Personas page, open the Goals tab and scroll to Credentials.

Fill in Label, a name you'll recognise, up to 80 characters. Then Username, up to 320 characters, and Password, up to 1,000 characters. Spaces in the password are kept as typed.

Choose Add credential.

Open the goal that needs it, and on its Info tab choose the label under Sign in with. Then choose Save changes.

The Goals tab shows which login each goal Signs in as, or No login.

Labels that need a second look

A label containing the word admin, administrator, prod, production, root, superuser or owner sounds like a real or powerful account. PersonaMark won't save one without a person confirming it: the form says "This label sounds like a real or powerful account. Persona runs should use a test account." If the account really is a test account, tick Use this label anyway and add it again. Otherwise, use a different account.

How a login is kept

  • It's encrypted when you save it, and it can't be shown again, to you or anyone else. Members of the organization see only its label.
  • Only the worker that runs the agent can decrypt it, at the moment a run needs it.
  • To change a login, delete it and add it again, then choose it on the goal once more.

What never reaches a model or a log

The agent never sees the username or password. When it needs to sign in, it asks for the username or the password to be typed into a field, and the worker types it. The values never go to the model, into the run's step log, or into the server's logs.

The screenshots are handled with the same care:

  • Once the login is typed into a field, that field is blanked out in every screenshot the run saves.
  • A step that typed a login is never shown to the scorer, nor is any later step on the same page, since a page can repeat what was typed back.
  • The run's own screenshots are kept for 30 days after a run that logged in, rather than 90. See data retention.

A run keeps its own copy of the persona and goal it used, but never the login.

Deleting a login

In Credentials, choose Delete beside it and confirm. This can't be undone. The encrypted login is removed, and any goal that signed in with it goes back to No login.

On this page