Skip to main content
Treat the first day like you used to: get access, get the URL, get the checklist, agree how you’ll report. SimpleUAT holds those pieces so you don’t invent a new folder structure per client.
1

Create Client Project

Name = what you’ll put on the invoice. Type = closest platform (web, ios, api, and so on).
2

Environment first

If they only gave you a staging URL, that’s enough to Add First Environment. Password notes can live in the environment description or in case preconditions (same as the header cells in the old sheet).
3

Load tests

Pack if they have no script. Import if they sent Excel/CSV/Word/PDF. Manual if it’s a tiny smoke. Wizard if you want starter structure. Choose setup.
4

Personas

Admin vs shopper vs “read-only finance”: Create First Persona. Access types and login methods exist on the persona. That’s who you log in as, not a separate user-management product.
5

Connect before you're done testing

Ask for their Delivery ID or send an invitation now. PENDING until they approve. Delivery fails if you wait and they’re still pending. Connect.
6

Cycle + run

Create First Cycle, include the cases that are in scope (not every pack case if you installed a large pack). Start a run.
If you are a viewer on the org, you will not be able to create this structure. That’s a role limit, not a missing product. Missing feature.

Reuse across clients

Packs and what is safe to copy.

Client has no account

Invitation, signup, pending connection resumes.