> 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/cloud/da/web-interface/ui-customization/vault-content-types.md). # Indholdstyper for bokse Konfigurer indholdstyper for bokse i Devolutions Cloud, f.eks. bokse af typen Standard, Hemmeligheder, Virksomhed og Legitimationsoplysninger, for at begrænse tilladte posttyper. Indholdstyper for bokse begrænser de posttyper, der kan **oprettes** i en bestemt delt boks. Typen kan vælges, når De [opretter eller redigerer en boks](/cloud/da/web-interface/administration/management/vaults/create-and-manage-vaults.md). Eksisterende poster påvirkes ikke af en ændring af bokstypen og kan stadig bruges, ændres, flyttes, importeres og eksporteres. Der findes fire indholdstyper for bokse: * ***Standardboks***: En standardboks, hvor alle posttyper er tilgængelige. * ***Hemmelighedsboks***: Hemmelighedsposter, der bruges i DevOps- og CLI-processer. * ***Virksomhedsboks***: Poster som oplysninger, kontakt, aktiver eller dokumenter. Nyttig i virksomhedsorganisering. * ***Legitimationsboks***: Poster til alle typer legitimationsoplysninger, ikke kun hemmeligheder. Her er den fulde liste over tilgængelige posttyper for hver type boks:
PosttyperStandardboksVirksomhedsboksLegitimationsboksHemmelighedsboks
SessionXKun posten Websted
FjernadministrationX
LegitimationspostXKun posten Brugernavn og adgangskodeXKun posten Hemmelighed
OplysningerXX
MappeXXXX
KontaktXX
DokumentXX
SkabelonXXXX
--- # 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.devolutions.net/cloud/da/web-interface/ui-customization/vault-content-types.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.