> For the complete documentation index, see [llms.txt](https://help.cryoserver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cryoserver.com/powered-by-solar-archive/using-the-archive/spaces/adding-to-a-space.md). # Adding to a Space Adding Entries to a Space {% hint style="info" %} This is applicable to users connecting to either: archive.cryoserver.online or eu.cryoserver.online. Not for on-premises or other .cloud environments. To learn more about switching to the new .online environments please contact your Account Manager or email {% endhint %} When you've found what you've been looking for, it's effortless to add them to a space for safekeeping. You can add individual or multiple emails at a time to multiple spaces. Hooray! ### **Adding Emails to Space** To add a single email to a space, select the emails you would like to add from your results by clicking their checkboxes and adding them to your current selection. Once you have chosen your desired emails, in the sub-navigation bar underneath the main navigation bar you will see a button called **"Save to Space" -** go ahead and click this button.

Selecting emails and "Save to Space"

On clicking the **"Save Space"** button you will have the options to either select one of your already created spaces or create a brand new space to store these emails. On clicking of a space, it will automatically save these emails to that chosen space. {% hint style="warning" %} If saving a large number of emails, it may take several seconds for them to appear in your space. {% 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://help.cryoserver.com/powered-by-solar-archive/using-the-archive/spaces/adding-to-a-space.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.