> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/it/concepts/basic-concepts/vaults.md).

# Casseforti

Le casseforti in Devolutions Server sono contenitori che segmentano gli spazi di lavoro in compartimenti logici come team o clienti con autorizzazioni dedicate.

Le casseforti in Devolutions Server sono contenitori che segmentano il suo spazio di lavoro in compartimenti logici come team, clienti o zone di sicurezza. Ogni cassaforte contiene le proprie voci e la propria struttura di cartelle, con proprietari e autorizzazioni dedicati e tipi di contenuto facoltativi come credenziali, segreti o informazioni aziendali. Limitare l'accesso a livello di cassaforte semplifica la gestione dei diritti, mantiene pertinenti i risultati di ricerca e supporta la privacy sia per le casseforti condivise sia per quelle personali degli utenti.

Ad esempio, potrebbe creare casseforti separate per produzione e staging, concedere agli auditor l'accesso in sola lettura a una cassaforte di reportistica e assegnare a ogni amministratore una cassaforte utente privata.

#### Argomenti correlati

* [Casseforti](/server/it/web-interface/administration/user-and-security-management/vaults.md)
* [Accesso alle casseforti in Devolutions Server](/server/it/web-interface/vault-access-in-devolutions-server.md)
* [Cassaforte utente](/server/it/web-interface/user-vault.md)


---

# 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.devolutions.net/server/it/concepts/basic-concepts/vaults.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 `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.