Manta handbook · 7 of 10
How to Organize Projects, Environments, and Your Team in Manta
A quick guide to structuring Manta for a real team: one project per app, environments for staging and production, and shared access so everyone sees the same runs and findings.
By the end of this guide, Manta will be set up so your whole team shares the same projects, runs, and findings — no one working from a private view.
The hierarchy
Manta is organized as organization → projects → runs. An organization is your company or team. A project is one application. Runs, the navigation map, and findings all belong to a project.
Step 1 — One project per application
Create a project for each distinct app you test — your main product, an admin console, a marketing site if it has real flows. Keep them separate so each has its own history and map rather than a mixed pile of runs.
[Screenshot: the projects list with a few applications]
Step 2 — Set up environments
Within a project, configure the environments you test against — typically staging and production, each with its base URL and a dedicated test account. This lets you start a run against "staging" without re-entering the URL and credentials every time, and keeps production runs clearly separate.
[Screenshot: a project's environments settings, staging and production configured]
Step 3 — Invite your team
Add the people who need to see results — developers, QA, PMs. Everyone in the organization sees the same projects, runs, and findings, so a bug one person triages is visible to whoever fixes it. There's no per-person private state to keep in sync.
[Screenshot: the team members screen with several people invited]
Step 4 — Agree on a convention
A little shared convention keeps a team's runs legible:
- Run against staging for pre-release checks; reserve production runs for monitoring-style checks.
- Keep the plain-English suites for critical journeys in one place everyone knows about.
- Decide who owns triage for each project's findings.
Tips and common mistakes
- Don't put multiple apps in one project. The navigation map and run history stop being useful when they're mixing two products.
- Use a dedicated test account per environment, not a personal or customer login.
- Keep environment URLs current — a stale staging URL is the most common reason a run can't connect.
What to try next
- How to Set Up Run Notifications — so the team hears about failures without checking the dashboard.
- Testing for QA teams — how a team divides up the work.
Start free and set up your first project.
Try it on your own app
Point Manta at a URL and see what it finds — no scripts, no setup. Free, no credit card.