# You built the workspace. Now test it with a team.

A shared workspace behaves differently when people have different roles and competing priorities. Jango lets developers and teams bring several test accounts into the same workflow and observe the handoffs.

## Give each account a different job

Set up an owner, an editor and a viewer using your app’s own permissions. Ask the owner to create a task, the editor to update it and the viewer to find the latest status. Jango directs the participants; your app remains responsible for enforcing access.

- Invite a teammate and check which workspace they enter.
- Assign a task, add a comment and inspect it from the assignee’s account.
- Change a shared item and compare the state visible to other participants.
- Explore a role change and check which controls remain visible.

## Try a handoff before your users do

Ask a project lead to create a launch checklist and assign a review. Ask the reviewer to request a change, then have the lead update the task. Join as a third collaborator and follow the activity. Check that the latest state and the next action are clear from every role’s perspective.

## Revisit a workflow after a fix

Keep the cast’s roles and saved login state, then direct another run through the changed flow. Use named starting points for setup that would otherwise need repeating. Reset your app’s test data separately when you need the same underlying records.

## Pair exploration with exact tests

Independent browser sessions are useful for finding confusing handoffs and visible state disagreements. They do not prove concurrency correctness or permission security. Keep API-level authorization tests and controlled concurrency tests for those guarantees; use Jango to explore what participants experience.

[Open Jango](https://usejango.com/#downloads)