Test-account login guide
This page only appears on our test sites — never on the real product. The accounts and password below are fake and exist only here, so you can explore BOLO safely.
Signing in
- On the sign-in screen, enter one of the emails below — the everyday one is
admin@memphispd.test. - Enter the shared password (next section). No code from your phone is needed on test sites.
- You land in a fully populated BOLO app with sample bulletins to explore.
The shared password — and the one rule
Every account below uses the same password:
PreviewSeed!2026
It's a throwaway value, safe to share inside the team — it only ever protects fake data on test sites. If it ever stops working, an operator may have rotated it; check the team channel for the current value.
The one rule: never change a test account's password to your own. These accounts are shared. If you change one to something only you know, you lock out the whole team until an operator resets it. If the app ever forces a change, set it back to the shared value above.
Use the seed accounts for basic testing — make your own for in-depth testing
Treat these pre-made accounts as a shared demo set: sign in, click around, check that a feature works. But the moment you want in-depth or destructive testing of an organization or its people — changing org settings, inviting/suspending/removing users, deleting things, reshuffling roles — create your own organization and accounts and do it there. Don't reconfigure a seed account's own org or its people; the whole team (and our automated tests) rely on this set staying intact.
The accounts
Every test site is pre-loaded with the same fake organizations and people, covering the real shapes of BOLO. All of them use the shared password above.
Memphis Police Department
The main law-enforcement agency (Tennessee). Where most testing happens — its people cover every permission level.
| Sign-in email | Name | Role & purpose |
|---|---|---|
admin@memphispd.test | Alex Admin | PD Admin — the everyday account. Full department admin: manage people, approve, create, export. Start here. |
sergeant@memphispd.test | Sam Sergeant | Supervisor — supervises the Detective Bureau; sees and works the approval queue. |
detective@memphispd.test | Dana Detective | Detective (regular officer) — create and view bulletins; submissions route to the sergeant. |
viewer@memphispd.test | Vera Viewer | Read-only — can view but cannot create, export, or print. See the locked-down experience. |
geo@memphispd.test | Geo Tester | Detective with nearby-bulletins (geo) discovery on (50-mile radius around Memphis). |
lifecycle@memphispd.test | Riley Reserve | Detective reserved for suspend/reactivate testing. Leave it alone unless that's what you're testing. |
Onboarding Test Agency
A separate little police agency (its own domain, onboard.test) whose two users have never completed BOLO's first-run questions, so they still see the welcome prompts.
| Sign-in email | Name | Role & purpose |
|---|---|---|
onboard-pick@onboard.test | Pat Newcomer | Detective — drives the first-run "pick your interests" path. The prompt shows only once ever. |
onboard-skip@onboard.test | Sky Newcomer | Detective — drives the first-run "skip it" path. The prompt shows only once ever. |
Shelby County Sheriff's Office
A second law-enforcement agency near Memphis, actively partnered with Memphis PD.
| Sign-in email | Name | Role & purpose |
|---|---|---|
admin@shelbycounty.test | Casey Chief | PD Admin — receives cross-agency shares from Memphis PD in "Shared with Us". |
officer@shelbycounty.test | Sam Sheriff | Detective — a line officer at the second agency. |
Bluff City Mercantile
A retail chain (loss-prevention side) with two stores, partnered with Memphis PD. Its bulletins show up on the police side under "Shared with Us".
| Sign-in email | Name | Role & purpose |
|---|---|---|
lp@bluffcitymercantile.test | Morgan Loss-Prevention | Retail Admin — creates store bulletins and shares them with police. |
Riverbend Outfitters
A second retailer, not linked to Memphis PD — used to test bulletins being passed along across the retail network.
| Sign-in email | Name | Role & purpose |
|---|---|---|
lp@riverbendoutfitters.test | Riley Retail-Security | Retail Admin — receives passed-along bulletins. |
Metro Loss Prevention Partners
A security firm granted access to file and read reports on behalf of Bluff City Mercantile — used to test the "which client is this for" flow.
| Sign-in email | Name | Role & purpose |
|---|---|---|
manager@metrolosspreventionpartners.test | Riley Region-Manager | Security-company manager — acts on behalf of a retail client. |
Platform operator (no agency)
The super admin — belongs to no single agency and runs the system-admin area. Powerful; use sparingly (see the guide).
| Sign-in email | Name | Role & purpose |
|---|---|---|
super@recalltech.test | Sky Operator | Super admin — system-admin area at /app/admin/... . Don't make sweeping changes on a shared site. |
Super admin — use sparingly
super@recalltech.test ("Sky Operator") can see and change things across the whole platform,
and it lands in the system-admin area (/app/admin/...), not the normal dashboard. Because one
person making sweeping changes as super admin can break the test site for everyone else, reach for it
only when the thing you're testing actually lives in the system-admin area, and avoid sweeping or
destructive changes on a shared site while others are working.
A few things to try
- A full police experience — sign in as
admin@memphispd.test: the dashboard is populated with sample bulletins. - The read-only experience — sign in as
viewer@memphispd.test: no create, export, or print. - The approval queue — sign in as
sergeant@memphispd.test. To test it end to end, create your own bulletin as the detective and approve that one. - Retail ↔ police sharing — as
admin@memphispd.test, look under "Shared with Us"; then sign in aslp@bluffcitymercantile.testfor the retailer's side. - One agency sharing with another — sign in as
admin@shelbycounty.test(partnered with Memphis PD).
Good manners on a shared site
- Someone else may be mid-test. For destructive testing, use your own org/accounts (above) or a fresh per-PR preview.
- Don't approve or reject the pre-made pending bulletin ("Aggravated Assault — Beale Street") — it's reserved for the automated tests. Create your own to test approvals.
- Don't change the seeded passwords — it's the most common way to lock the team out.