Organization access
Authorize an MCP client in one organization and choose what it can do.
An MCP client acts as you, in one organization. It reaches the same projects you can open there, and only does what you approve on the consent screen.
Authorization flow
When a client connects, Autonomy opens a browser page:
- If you aren't signed in, click Sign in and sign in to Autonomy QA.
- If no organization is active, the page asks you to Choose an organization. The client can reach one organization; you can connect it again for another.
- The consent page, titled with the client's name, shows the organization, your role in it, and what the client will be able to do. Click Authorize, or Cancel to share nothing.
- When the page says the client is connected, close the window and go back to the client.
The sign-in link from a client works once and only for a few minutes. If you see "This link has expired", start the connection again from the client.
If your account isn't in an organization yet, create one in Autonomy QA first, then connect again. Only connect tools you trust.
One organization per connection
Each connection reaches the organization you chose when you authorized it. To work in another organization, connect the client again and choose that one.
What the client can reach
- Members: "It acts as you, only in the projects you can open." The client sees and changes only the projects you've been given.
- Owners and admins: "It acts as you." The client reaches every project in the organization.
The client also stops working in an organization if you leave it.
Permissions
The consent screen lists what the client asked for. Every client gets read access; the rest appear only when the client requests them.
| Consent screen | Scope | Tools |
|---|---|---|
| Read projects, test cases, runs and issues | autonomy:read | Every list and get tool, autonomy_run_step_actions, autonomy_run_evidence |
| Create and edit test cases | autonomy:test_cases:write | autonomy_test_case_create, autonomy_test_case_update_steps, autonomy_test_case_archive |
| Create and edit test plans | autonomy:test_plans:write | autonomy_test_plan_create, autonomy_test_plan_set_members |
| Start runs | autonomy:runs:write | autonomy_run_trigger |
| Create and edit environments | autonomy:environments:write | autonomy_environment_upsert |
| File and update issues | autonomy:issues:write | autonomy_issue_create, autonomy_issue_comment, autonomy_issue_set_status |
| See your name and email address | openid, profile, email | |
| Stay connected until you disconnect it | offline_access |
Access tokens last one hour. With "Stay connected until you disconnect it", the client renews its token without asking you again. To stop a client, disconnect or remove the Autonomy server in the client.
Common mistakes
- Authorizing with an account that isn't a member of the organization you need.
- Choosing the wrong organization on the consent screen. Connect again and choose the right one.
- Leaving the browser signed in to another account. Sign out first, then connect again.
- Expecting a project you haven't been given. Ask an organization admin to give you access to it.
Didn’t find it?