> 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/contracts/users.md).

# Linked users

In the **Users** tab, associate users from your workspace with the document and give them a role: **Accountable**, **Responsible** or **Informed**. Click **Add a user**, then choose the user and their role.

Here is one way to split the roles for your documents:

* **Accountable**: the user in charge of validating that the document and the associated elements, as documented in Dastra, meet the organization's expectations. This role may differ from the signer of the document.
* **Responsible**: the user in charge of carrying out the actions needed to meet the requirements of the document. This could involve implementing data security measures, managing access or any other task required to comply with the terms of the contract.
* **Informed**: the users who need to be kept up to date on the progress and status of the document, without an active role in its validation or implementation. This can include management, project managers or other stakeholders.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-7d9bcf37a587d9ea7001a3c9426b82b1b0099beb%2Fcontracts-users-1.png?alt=media" alt="The Users tab of a document with one user for each of the three roles"><figcaption><p>Link users to a document</p></figcaption></figure>


---

# 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/contracts/users.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.
