> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/synced-tables/sync-schema-changes.md).
# Sync schema changes
Refresh a resource's schema after adding or changing tables and fields.
Refresh a resource's schema after adding or changing tables or fields in the source. A schema refresh updates the structure Jet Admin discovers; refreshing record values is a separate task.
## Before you start
Make the schema change in your source first. Use an administrator account in Jet Admin, and check that the resource's credentials can access the affected tables and fields.
## Refresh the schema
1. Open **Data** and select the resource you changed.
2. Open the resource's **More** menu and select **Sync Structure**. Some resource interfaces label the schema-refresh control **Sync**.
Select Sync Structure from the resource menu. This image shows the command, not a completed refresh.
3. After the refresh, open the affected table or collection.
4. Check that the new table or field appears.
### REST API resources
Open the REST API resource and use its schema-sync control after changing the structure exposed by the API.
## If a table or field is still missing
Check that the change exists in the source and that the credentials used by Jet Admin can access it. Confirm that you refreshed the intended resource.
For further checks, see [A data resource is failing to sync](/faq-and-troubleshooting/a-data-resource-is-failing-to-sync.md).
## Refresh record values
If the table structure is correct but record values are stale, use **Sync now** for a synced connection. See [Sync Options](/user-guide/synced-tables/refresh-data-and-manage-sync.md) for sync status, manual refresh, events, and interval settings.
---
# 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.jetadmin.io/user-guide/synced-tables/sync-schema-changes.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.
