> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/claims.md).
# Claims
This page provides details on how to view and manage claims.
The Claims list can be found in the sidebar under the module labeled "Claim". Opened, displays a list of available claims (see Figure 1).
{% hint style="info" %}
This list features the grid functions, such as sorting, filtering, aggregation, resizing columns, and much more. For more details on features and usage, please refer to the[ data grid section](/release-8.31/voyage-management-system/step-by-step-guides/data-grids.md).
{% endhint %}
Figure 1. Claims List
## Create and Edit a Claim
To create a claim, click the **+** icon located in the top right corner of the claims page (refer to Figure 1). For more information on how the claim creation proceeds, please visit the [Create a Claim](/release-8.31/voyage-management-system/step-by-step-guides/claims/create-a-claim.md) page.
To modify an existing claim, click on the open drawer icon, which is usually found in the leftmost column of the grid. This action will open the [Claim drawer ](/release-8.31/voyage-management-system/step-by-step-guides/claims/claim-drawer.md)for the selected claim.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/claims.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 `build a script that syncs our docs to a CMS` 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.
