From 3d959678864b27bb658a05f085ed30872b6ecea8 Mon Sep 17 00:00:00 2001
From: Marco Del Tufo <marco.deltufo@exact-lab.it>
Date: Wed, 13 Sep 2023 07:10:06 +0000
Subject: [PATCH] Update installation-and-configuration-guide.md
---
.../installation/installation-and-configuration-guide.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/system-admin-documentation/installation/installation-and-configuration-guide.md b/docs/system-admin-documentation/installation/installation-and-configuration-guide.md
index b6a6f6ab98a..faaa813cd44 100644
--- a/docs/system-admin-documentation/installation/installation-and-configuration-guide.md
+++ b/docs/system-admin-documentation/installation/installation-and-configuration-guide.md
@@ -1349,7 +1349,7 @@ is configured, then for the query database configured with key `db1`:
- only a user who has the `OBSERVER` role in data space `CISD` is
allowed to execute a query.
-For query databases that do not belong to a space but that have a column with any of the [magic column names](../../../user-documentation/general-admin-users/custom-database-queries.md#hyperlinks), the query result is filtered on a per-row basis according to what the user executing the query is allowed to see. In detail this means: if the user executing the query is not an instance admin, filter out all rows which belong to a data space where the user doesn't have a least the observer role. The relationship between a row and a data space is established by means of the experiment / sample / data set whose `permId` is given by one of the magical column names.
+For query databases that do not belong to a space but that have a column with any of the [magic column names](../../user-documentation/general-admin-users/custom-database-queries.md#hyperlinks), the query result is filtered on a per-row basis according to what the user executing the query is allowed to see. In detail this means: if the user executing the query is not an instance admin, filter out all rows which belong to a data space where the user doesn't have a least the observer role. The relationship between a row and a data space is established by means of the experiment / sample / data set whose `permId` is given by one of the magical column names.
For sensitive data where authorization needs to be enforced, there are
two setups possible:
--
GitLab