> 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/organization-settings.md).

# Organization settings

{% hint style="info" icon="user" %}
Audience: ADO **organization administrators**.
{% endhint %}

### About organization settings

This is where you connect Coverage Analysis to the outside world, once for the whole organization: to your SeaLights account (where coverage data comes from) and to your ADO organization (where your work items live). Every project in the organization uses this connection, so you set it up once and project admins can focus on their own settings.

Until both connections are set, no coverage data appears in any project.

<figure><img src="https://1255034336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxSagdStwf6CJ9cI6lA68%2Fuploads%2FRoyq4ubp7UJ36nPlfckc%2FScreenshot%202026-10-30%20at%2014.34.34.png?alt=media&amp;token=fd8000fc-21a5-4bb5-93ac-e0441957f61f" alt=""><figcaption></figcaption></figure>

### Open the page

1. In ADO, select **Organization settings** (bottom-left).
2. Under **Extensions**, select **Coverage Analysis**.

The page, **SeaLights Coverage Analysis — Org Settings**, contains one card: **Connectivity & Integration**. Its status shows **Defined** when both connections are in place.

### Connect to SeaLights

**SeaLights API Token** establishes the connection between ADO and your SeaLights account.

1. Generate a token in SeaLights. The **Learn how to generate a token** [link](https://docs.sealights.io/knowledgebase/settings/token-access-and-management#api-tokens) on the page explains how.&#x20;
2. Paste the token into the **API Token** field and verify it. SeaLights confirms that the token is valid. If it isn't, you're asked to check the token or generate a new one.
3. Once the token is accepted, the field is locked and masked.

### Connect to ADO

**ADO API Token** lets the extension read your work items, their hierarchy, and project information.

1. Create a Personal Access Token in ADO: **User settings → Personal access tokens → New token**.
2. Give it read access to **Work Items** and to **Project and Team**.&#x20;
3. Paste it into the **ADO Token** field and confirm.

### Changing or replacing a token

Select **Change** next to a token, enter the new one, and confirm. Do this whenever a token expires or is revoked.

{% hint style="info" icon="lightbulb-on" %}
**Tip:** Personal access tokens expire. Note the expiry date and replace the token beforehand. When it lapses, coverage stops loading until a new token is entered.
{% endhint %}

### What's next

Project admins can now set up their projects: [Project settings](https://claude.ai/chat/05-project-settings.md).


---

# 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/organization-settings.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.
