AdaDocsAda AI for Azure DevOpsTry the demo

Permissions

Extension scopes

Scope Why it is needed Used by
vso.wiki_write Read Wiki pages (including the persona pages of an earlier version, for a one-time import); save edits (version-checked) and create pages (create-only) after the user confirms Hub, documentation assistant, Ask the Wiki
vso.work_write Read and query work items, types, area and iteration paths; create or update work items (also a connecting Epic and its links), create iterations and add them to a team's sprints, each after the user confirms Hub, Ask about Work Items, Ada on work items, Create Sprint Schedule
vso.project List projects and teams, read the process template Hub
vso.code Read-only search of merged and active pull requests, pull-request metadata (title, description, branches, file paths, commits, linked work items), the repository list, and repository files for architecture documentation, debates and pull-request reviews. Reviews post nothing to the pull request Pull-request docs, organization settings, Generate Project Documentation (architecture), Debate Architecture, Review a Pull Request
vso.build Read-only classic (designer) build pipeline definitions, for the deployment view Generate Project Documentation (architecture)
vso.release Read-only classic release pipeline definitions and their stages, for the deployment view Generate Project Documentation (architecture)

Not requested: code write, build or release execution, identity management, security management, organization administration. Pipelines are only read, never created or changed.

The extension never asks for a personal access token. Azure DevOps calls from the extension run with the signed-in user's own permissions, so there users can only read or change what they could anyway. The exceptions are below. Extension data (the backend configuration and project templates) is the extension's own storage and needs no scope.

Exceptions: features that read with the backend's own access

Two features answer from more than the asking user may be able to open, on purpose:

Both read with the backend's own identity, not the user's. A support agent, for example, needs answers from every board, every repository and the monitoring system without access to each of them. So anyone allowed to use these two features can get answers, with quotes, from everything administrators chose for them. Administrators decide who that is: choose the projects, repositories and log sources with that in mind, and limit who can use the features with the access settings.

The jobs that administrators set up also run with the backend's own identity, as SECURITY.md and DATA-HANDLING.md describe for each:

The hub is a top-level group in the project sidebar (ms.vss-web.project-hub-groups-collection); the work-item form group is named "Ada". Neither needs a scope.

Organization-level actions

Action Who Notes
Install the extension Organization or project collection administrators (Marketplace) Re-approval is required when scopes change
Configure the backend Project Collection Administrators (admin page) See the limitation in ADMIN-CONFIGURATION.md
Use AI features Users allowed by the organization's backend (tenant, organization, users, groups, app role) Enforced by the backend
Write Wiki pages or work items Users with the corresponding Azure DevOps permission Always after explicit confirmation

Normal features need no administration permissions.

Administrators can narrow this further under Organization settings > Ada AI > Access (backend 1.64.0): limit tabs and single quick actions to Azure DevOps teams and groups, and turn on Read-only Ada, under which Ada changes nothing in Azure DevOps for anyone: the extension and the backend both refuse every change. The extension's scopes stay as listed above, since Azure DevOps grants them per extension.

Backend permissions (reference deployment)

No identity gets Owner or Key Vault Administrator for runtime use.