> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/gerer-les-exercices-des-droits/faq.md).
# FAQ
## Do applicants receive an email notification when a claim is closed?
Applicants receive a notification email when a claim is closed only if the "Send a notification to" box is checked when closing the claim:\
## Once the request has been closed, how many days does the requester still have access to the secure area where they can view exchanges concerning their request?
Once the request has been closed, the requester still has access to this area for 60 days.
## How does the requester's email verification work?
When a request is submitted from the public form, the requester receives a confirmation email containing a **validation link** and a **6-digit code**. The request is only taken into account once the address has been validated.
* The link and the code are valid for **24 hours**. This duration cannot be configured.
* After several incorrect code entries (4), further attempts are **blocked for 30 minutes**.
* If the deadline is exceeded, the requester must submit a new request.
## Why can't a requester submit a new request?
The same requester (same email address) cannot submit a second request of the **same type** in the same workspace while the previous one, submitted less than 24 hours ago, has not been closed.
## What is the maximum length of a message in a request?
Messages exchanged with the requester, the public form message and closure reasons are limited to **3,000 characters**. A message can contain up to **20 attachments**.
---
# 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://doc.dastra.eu/en/features/gerer-les-exercices-des-droits/faq.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.