From c6b5f29a6d60c6bdfd9c40e0d50f160ba7a12091 Mon Sep 17 00:00:00 2001
From: Tim Berthold <75306992+tmberthold@users.noreply.github.com>
Date: Mon, 2 Dec 2024 09:30:19 +0100
Subject: [PATCH] Update faq.md

---
 docs/getting-started/documentation/faq.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/getting-started/documentation/faq.md b/docs/getting-started/documentation/faq.md
index 4f3091a2b..b2d798891 100644
--- a/docs/getting-started/documentation/faq.md
+++ b/docs/getting-started/documentation/faq.md
@@ -88,3 +88,7 @@ Yes, the architecture relys on the data provider directly connecting to the data
 ### What happens during policy evaluation, if a not-supported contraint is used in a policy?
 
 If the EDC encounters a constraint it does not recognize within a policy, the EDC is designed to simply ignore that constraint during the evaluation process of the access- or contract-policy. This means that the unrecognized constraint will not impact the outcome of the evaluation.
+
+### Is it possible to exchange data between different organizations in a data space?
+
+If two connectors, regardless of their organization, are in the same data space, they can request the catalog from each other and then see the data offers that they are allowed to see according to the access policy and also negotiate successfully if they meet the contract policy.