Test one flow across several accounts.

Some bugs only show up between accounts: an invitation that never arrives, or a member who can open billing. Multi-user tests give each role its own browser and account. This is a preview.

Role based coverageExample
One workspace. Three permission paths.Guest · member · admin
GuestPublic access
northstar.test
Browse plans

Starter$9 / month

Pro$24 / month

Private projects hidden
MemberProject access
northstar.test / workspace
Project dashboard

Website launchCan edit

API gatewayCan edit

Billing restricted
AdminWorkspace access
northstar.test / people
People & permissions

Priya RaoOwner

Sam ChenMember

Role changes observed
Each path checks a different boundary. Choose the roles your app needs to support.

One browser per role

Admins, members and guests each get a separate browser and identity.

Plan the roles first

Describe the roles and what each should do. Review the plan before anything runs.

Preview

Multi-user tests are in preview. Talk to us before planning a large test.

Plan a multi-user test

List the roles and what each should do, such as “an admin invites a member” and “the member accepts the invitation and can’t open billing.” Molar turns them into a plan you can review, then runs each role in its own browser.

  • One browser per role
  • A plan you review first
  • A result for each role
Plan a check for each roleIllustrative example
Guest
Create an account Buy a plan

Separate browser and identity

Member
Accept an invitation Open a project

Separate browser and identity

Owner
Invite a member Review billing

Separate browser and identity

Preview Planned checks only. No run results are shown here.

See it in a recorded example

The team-invitation example shows an admin and a member in separate browsers, with the invitation email in a test inbox. That example is a scripted test, not an AI agent run.

Watch the invitation example
Role and permission matrixIllustrative example
Workspace accessexample.acme.test site-specific account
RoleProjectsBillingMembers
Owner edit manage invite
Member edit— none— view
Invitee— pending— none— none
Verification code: member workspace opens

Frequently asked questions

Have a specific workflow in mind?
Talk to us

What should we bring?

Your app, the roles you need and a task for each role. We’ll confirm what the preview supports.

How many browsers can run at once?

During the beta, hosted capacity is one run at a time across Molar. Talk to us before planning a larger test.

Is there a multi-user example?

The team-invitation example shows separate admin and member browsers with Auth and Email Clones. It is a scripted test, not an AI agent run.

Try a multi-user test.

Create a free workspace, then tell us which task you want to try in the preview.

Free during the beta. No card.