> For the complete documentation index, see [llms.txt](https://docs.lumidb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumidb.com/archive-management.md).

# Archive management

Control who can see what, keep track of storage and answer security questions for your organization's archive.

Use these pages if you look after your organization's archive: who has access, how much data you hold, and what your IT and security teams need to know.

* [Administer your organization](https://docs.lumidb.com/archive-management/administer-your-organization.md): add people, choose their roles and see your organization's data.
* [Limits and storage](https://docs.lumidb.com/archive-management/limits-and-storage.md): what counts toward your storage and when to contact us.
* [Security and hosting](https://docs.lumidb.com/archive-management/security-and-hosting.md): where your data is stored and how access is controlled.
* [API keys](https://docs.lumidb.com/archive-management/api-keys.md): create, review and revoke the keys your tools use.


---

# 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.lumidb.com/archive-management.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.
