> 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/investigations/organising-investigations.md). # Organising investigations ### Organise investigations using tags Tags provide a flexible way to organise investigations according to your organisation’s workflows. #### Examples of potential tags include: * Priority levels * Product areas * Work programmes * Review categories * Team responsibilities Tags are shared across the organisation and are available to all users. A single investigation can have multiple tags. Using tags consistently makes it easier to locate, review and prioritise investigations. ### Assign tags to an investigation #### To apply tags: 1. Open an investigation. 2. Locate the Tags section. 3. Select one or more tags. 4. Click Close panel to save any changes. The selected tags become part of the investigation and are available for filtering and reporting. Tags may be added, removed or changed at any time. ### Filter investigations by tags Tags can be used to find specific groups of investigations. #### To filter investigations: 1. Open the Investigations area. 2. Open the filter options. 3. Select one or more tags. 4. Apply the filter. The list displays investigations matching the selected tags. #### Filtering by tags can be useful when: * Preparing team meetings * Reviewing high-priority work * Monitoring ongoing assessments * Managing specific projects --- # 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/investigations/organising-investigations.md?ask=&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.