> For the complete documentation index, see [llms.txt](https://docs.subsalt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subsalt.io/administration/data-use-agreements.md).

# Data use agreements

### Set data use agreement policies

Subsalt provides a mandatory data use agreement for data consumers in most configurations. If your instance supports it, organization admins can set the policy for data use agreements as it applies to internal or external users.

The policy options are:

* **Required**: Users must accept the data use agreement for the organization before they can query any database.
* **Skip**: Users will not be required to accept, and will not see, a data use agreement.

The audiences for policy options are:

* **Internal**: Users that are a part of the organization that the database is associated with.
* **External**: Users outside of the organization. Access to specific databases for the organization has been shared explicitly.


---

# 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://docs.subsalt.io/administration/data-use-agreements.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.
