> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/administration/designer/design-a-database/save-your-database-design.md).
# Save your database design
{% hint style="info" %}
User permissions: Administration > Databases and Sync
{% endhint %}
When you are finished designing or modifying a database, you need to save your changes.
In the top right corner of the Designer, click **Save**.
You then have the option to add a comment. The addition of comments is good practice as they're very useful for version control and troubleshooting. They help you keep track of design versions and remind you of the purpose of building the database or making changes. The comment is displayed in the **Versions** tab of Designer.
If you don't want to add a comment, click **Save**. If you do want to add a comment, click **Comment and Save**, then type your comment and click **Save**.
Next step in the design a database process: [Build your database](/administration/designer/build-a-database.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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.phocassoftware.com/administration/designer/design-a-database/save-your-database-design.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.