---
title: "Known limitations | Grafana Labs"
description: "Understand the current limitations and constraints of Git Sync."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Known limitations

Git Sync has certain limitations you should be aware of when planning your dashboard management workflow. Understanding these constraints helps you design effective processes and avoid unexpected behavior.

## Current limitations

Be aware of the following limitations when using Git Sync:

Synced resources

- You can only sync dashboards and folders. Refer to [Supported resources](/docs/grafana/next/as-code/observability-as-code/git-sync/#resource-support-and-compatibility) for more information.
- If you’re using Git Sync in Grafana OSS and Grafana Enterprise, some resources might be in an incompatible data format and won’t be synced.
- Full-instance sync is not available in Grafana Cloud and is experimental in Grafana OSS and Grafana Enterprise.
- If you want to manage existing resources with Git Sync, you need to save them as JSON files and commit them to the synced repository. Use `grafanactl` or open a PR to import, copy, move, or save a dashboard. Refer to [Export non-provisioned resources from Grafana](/docs/grafana/next/as-code/observability-as-code/git-sync/export-resources/) for more details.
- Restoring resources from the UI is currently not possible. As an alternative, you can restore dashboards directly in your GitHub repository by raising a PR, and they will be updated in Grafana.
- You cannot modify the permissions of a provisioned folder after you’ve synced it.

For detailed information about usage limits and quotas, refer to the [Git Sync usage limitations](/docs/grafana/next/as-code/observability-as-code/git-sync/usage-limits/) documentation.

In the next milestone, you’ll navigate to the Git Sync interface in Grafana Cloud.