Projects
One project per product, with its own test cases, environments, sign-ins, issues and memory.
A project is one product you test. Its test cases, test plans, runs, environments, sign-ins, issues, digests, memory and files stay inside it. Members, billing, run credit and integrations belong to the organization and are shared by every project.
Use one project per product that people use separately. A web storefront and the mobile app that goes with it can be one project with web and Android targets. Two frontends for different users, such as a buyer site and a seller site, are usually two projects, even when they share an API.
Create a project
Owners and admins create projects. Open Projects and click New project:
- Project name: up to 40 characters, such as "Marketplace web".
- What does it do?: optional. It helps teammates, and the agent reads it when it drafts steps.
- First environment: optional. Give it a name and a web URL, and it becomes the project's default environment. Leave it empty to add environments later.
A project's platforms come from its environments. Add an Android or API target to an environment and the project tests that platform. iOS testing is coming soon. See Environments.
Who can see a project
- Owners and admins see every project.
- Members see only the projects they're given. An admin sets them in Organization → Members, in the Projects column: All projects, some projects, or No projects.
- API keys reach every project in the organization. AI assistants connected through MCP act as the person who connected them, so a member's assistant sees only that member's projects.
A member with no projects sees "Ask an owner or admin to give you access to a project."
Project settings
Open a project and click Settings. Owners and admins can change settings; members can see them.
| Tab | What it holds |
|---|---|
| General | The project name, its description and the default environment for new runs. Renaming a project changes its URL. |
| Files | Files your tests can upload, such as a sample ID card or a contract PDF. Up to 15 MB each. Every file is checked for safety before a test can use it. Search inside files lets the agent find a file by what's in it. |
| Integrations | How this project uses the organization's integrations: its Slack channel, its Linear team or Jira project, and the test plan that runs on pull requests. |
| Danger zone | Archive the project. Admins only. |
Archive a project
Archiving stops a project's schedules and pull request runs. Its history, issues and digests stay readable, and nothing in it can be changed. Every page of an archived project says so, and owners and admins can click Restore project to make changes again.
Environments made before projects
Environments made before projects existed are listed on a project's Environments page under Environments without a project. Admins can click Move into <project>: its targets, sign-ins, issues and digests come with it.
When your organization moved to projects, Autonomy grouped your existing environments into projects by URL, app ID and name, and put each test case in the project of the environment it ran in. Anything it couldn't place is in a project called Other. Move test cases out of it as you go.
Didn’t find it?