> 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/trust-center/configuration/security.md).

# Security

Learn how to require authentication, control access to documents and filter the IP addresses of your Trust Center.

The **Security** section of the editing page gathers three settings: mandatory authentication, approval of document downloads and IP address filtering. You designate the Trust Center owners in the **Configuration** section.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-8d2c04c511bc3c741b1d0c0ce31e9fbe0d4a4499%2Ftrust-center-security-1.png?alt=media" alt="Security section of a Trust Center with both options and the IP filtering rules"><figcaption><p>The Security section of a Trust Center</p></figcaption></figure>

## Mandatory authentication

Turn on **Authentication required to access the Trust Center** to make sign-in mandatory. Visitors must then sign in to Dastra with an account of your organization before they open the portal. If an SSO is assigned to all users, they are directed to that SSO.

We recommend setting up [SSO](https://doc.dastra.eu/en/features/settings/sso.md) with automatic user creation: all your employees can then access the Trust Center without any particular role or permission.

## Owners

The **Owners** field is in the **Configuration** section. See [Homepage and general configuration](https://doc.dastra.eu/en/features/trust-center/configuration/home.md).

## Document access control

The **Require approval for file downloads** option only appears when the **Attachments** feature is checked. It is turned on for a new Trust Center.

When it is turned on:

1. Visitors see the list of documents but cannot download them directly. They submit an **access request** with their email address and a message.
2. The Trust Center owners receive an email that links to the request. If there is no owner, the organization owners receive it.
3. The owner opens the request, enters a **Justification of the decision** if needed, then clicks **Approve access request** or **Reject access request**. The visitor receives the justification by email.
4. If the request is approved, the visitor receives an email that contains a download link valid for 30 days.

Requests are handled in the **File access requests** screen, which lists all requests with their status. The link in the notification email opens it directly on the request concerned.

{% hint style="info" %}
When owners are designated, only they can approve or reject requests. Without an owner, requests are notified to the organization owners.
{% endhint %}

## IP address filtering

In this section, you can also define rules that limit access to your Trust Center to specific IP ranges. By default, without any IP filtering added by you, your Trust Center will be accessible to anyone with the access link, provided that the Trust Center is activated.

Click **Add IP filtering rule**, then enter the rule name and the start and end of the IP range. An IP address that belongs to none of the ranges is refused.

{% hint style="info" %}
This filtering is **separate** from the organization-wide [IP filtering](https://doc.dastra.eu/en/features/settings/ip-filtering.md), which does not apply to the Trust Center.
{% endhint %}


---

# 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/trust-center/configuration/security.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.
