> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/install-the-extension.md).

# Install the Extension

{% hint style="info" icon="user" %}
Audience: ADO **organization owners / Project Collection Administrators**.
{% endhint %}

### About this step

Installing the SeaLights Coverage Analysis extension adds User Story Coverage Analysis to your Azure DevOps organization. It is a one-time step. After installing, you connect the extension to SeaLights and ADO ([organization settings](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/organization-settings.md)) and then configure each project ([project settings](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/project-settings.md)).

### Before you begin

The extension is private: it doesn't appear when you search the Azure DevOps Marketplace. SeaLights shares it directly with your organization.

1. **Send SeaLights your ADO organization name.** This is the part after `https://dev.azure.com/` in your ADO address.
2. **SeaLights shares the extension with your organization** and sends you the extension link.
3. **Make sure you have the right permissions.** Installing requires organization owner or Project Collection Administrator rights.

### Steps

1. Open the extension link that SeaLights sent you.
2. On **Review extension details**, check the permissions the extension asks for:
   * Project and team (read)
   * Work items (read)
3. Under **Select an Azure DevOps organization**, choose your organization and click **Install**.
4. When the installation completes, select **Proceed to organization**.

### What's next

Connect the extension to SeaLights and ADO: [Organization settings](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/organization-settings.md).

### Troubleshooting

<table><thead><tr><th width="305.3515625">Symptom</th><th>What to do</th></tr></thead><tbody><tr><td>The link opens but your organization isn't listed</td><td>SeaLights shared the extension with a different organization name, or you're signed in to a different account. Confirm the name with SeaLights.</td></tr><tr><td>You can't find the extension in the Marketplace</td><td>This is expected. The extension is private. Use the link SeaLights sent you.</td></tr><tr><td>Install button unavailable</td><td>You need organization owner or Project Collection Administrator rights.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/install-the-extension.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
