From d09d571691814ece593b570034b4841f530b0ef2 Mon Sep 17 00:00:00 2001
From: Marc Bernard <59966492+mbtools@users.noreply.github.com>
Date: Wed, 7 Jan 2026 15:20:27 +0100
Subject: [PATCH] Update data config documentation for clarity

Clarify data config saving behavior and supported tables.
---
 src/user-guide/reference/data-config.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/user-guide/reference/data-config.md b/src/user-guide/reference/data-config.md
index a147716f7..fd7e2625a 100644
--- a/src/user-guide/reference/data-config.md
+++ b/src/user-guide/reference/data-config.md
@@ -12,8 +12,12 @@ abapGit can serialize and deserialize data from any SAP table. The data is seria
 
 From the "Repository View", use "Advanced > Data Config" to add the tables you want to include in your repository. Optionally, you can specify if initial values should be serialized, and provide a where condition to filter the data.
 
+:::info
+The data config is *not* saved locally. You must stage and push the Data Config, i.e. the files related to `TABU` objects, to your repository. If not and you exit abapGit, then next time the configuration changes are not there anymore.
+:::
+
 :::warning 
-For safety reasons, by default only customer-defined customizing tables are supported.
+For safety reasons, by default only customer-defined customizing tables or tables that are included in the repository are supported.
 
 You can allow other tables using a [exit `CHANGE_SUPPORTED_DATA_OBJECTS`](exits.md).
 :::