> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigilyze/searching-and-filtering/search-by-country.md).

# Search by country

To search for individual countries in the Qualitative view, set Geographical scope to Global. For instructions, see Change Geographical scope.

Search results can be limited to one or more reporting countries.

Searching for individual countries

Enter one or more countries in the Search bar.

Searching for regions and continents

1. Click **Filter** → **Country**.
2. Select Continent, WHO region, or Custom country groups. You can define your own Custom country groups.
3. Click **Save**.

The search results are updated to reflect the selected countries.

#### Why can’t I filter by country?

The available country options depend on the geographical scope currently applied to your account.

If the expected country options are not available:

1. Open your personal settings.
2. Review the current geographical scope.
3. Confirm whether you are working with the global scope. Country filter searches are available only in the Global Geographical scope.
4. Return to the search and try again.

Changing the geographical scope may affect which countries can be selected and how results are displayed.

 


---

# 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://support.who-umc.org/vigilyze/searching-and-filtering/search-by-country.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.