Warn users about sandboxing and public sharing (metabase#15951)

* Warn users about sandboxing and public sharing * Update docs/enterprise-guide/data-sandboxes.md Co-authored-by: Jeff Bruemmer <[email protected]> Co-authored-by: Jeff Bruemmer <[email protected]>
driphub · Jun 2, 2021 · 714ad35 · 714ad35
1 parent ad753b1
commit 714ad35
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/docs/enterprise-guide/data-sandboxes.md b/docs/enterprise-guide/data-sandboxes.md
@@ -131,6 +131,10 @@ This goes for both saved or unsaved SQL queries. The reason is that Metabase doe
 
 An important distinction to make is that you can use a saved SQL query in the _creation_ of a sandbox. One of the options for setting up a data sandbox allows you to display the results of a saved question instead of the raw table. In this situation, you might choose to use a SQL query to supply the results that you'd like to display to a specific user group instead of the raw table itself.
 
+#### Data sandboxes and public sharing don't play well together
+
+Public questions and dashboards can't be sandboxed. Sandboxing works by filtering data based on the group membership and user attributes of an authenticated user — so since a user doesn't have to log in to see a public question or dashboard, Metabase has no knowledge of who that user is.
+
 ---
 
 ## Next: embedding Metabase in your web app