> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/seascape-for-notes/seascape-flex/adding-new-databases-to-flex.md).
# Adding new databases to Flex
To add a new database to your Flex server, copy the database folder from your new web archive into the Seascape Flex archive.
In the below example, we show three database folders on the Seascape Flex server. Each folder is named using the Replica ID of the source Notes database:
To add an additional database, simply copy the Replica ID folder from the new web archive you created and paste it in the Seascape Flex archive:
After the new folder has been added, open the Seascape Flex control panel and click **Update archives**.
Next, a new window will appear showing our Seascape viewer Updater tool.
Choose the root folder of your archives, and click on **Update** button.
Once the update is completed, and the new archive is indexed, it will be connected with the Flex design elements such as the advanced search dialog and others.
{% hint style="info" %}
you will need to restart the Elastic search and Flex services, for the indexing to commence.
{% 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://docs.swingsoftware.com/seascape-for-notes/seascape-flex/adding-new-databases-to-flex.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.
