# Sisense Git Integration Limitations

> The Sisense Git Integration feature involves huge changes across the entire application resulting in the limitations as we keep improving it.

*Source: https://docs.sisense.com/main/SisenseLinux/sisense-git-integration-limitations.htm*

---

Last updated: June 11, 2026

|  |  |
| --- | --- |
| [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) |
| Launch     Grow    Enterprise | Cloud     On-Prem |

The Sisense Git Integration feature involves huge changes across the entire application resulting in the following limitations as we keep improving it:

- Dashboards and Data Models are the only currently supported asset types.
- Decomposed .json files of tracked assets (such as dashboards or data models) are stringified, and their code is sorted alphabetically. In assets such as Blox, this results in a change in the structure of the files. While Blox widgets will continue to function as expected, their initial structure is modified to alphabetical order. For more information, see [BloX](https://docs.sisense.com/main/SisenseLinux/overview-sisense-labs.md).
- HTTPS is the only supported authentication method for connecting to remote repositories.
- Merge and conflict resolution are not supported in the Sisense Git Integration GUI. The user will have to handle this on a remote repository first, and then Git pull in the updates to the Sisense project.
- The ability to edit changed files directly in the Sisense GUI is not currently supported.
- Multitenancy - Git can only be used in the main system tenant environment, not by the organization tenants.
- Folders are not tracked by Git ([Asset Translation and Management](https://docs.sisense.com/main/SisenseLinux/asset-translation-and-management.htm?tocpath=Git%20Integration%7C_____3#NontrackedEntities)). Therefore, promoting a dashboard that is included in a folder on the dev environment will not recreate this folder on the prod environment, resulting in the new dashboard being located in the general list of dashboards.
- Data Security is not tracked by Git projects. Therefore, changes will not be migrated between the environments.