From 17ffae0e827ed00aacc386a8d3eb6391394be9c1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dafydd=20Ll=C5=B7r=20Pearson?= Date: Thu, 14 Mar 2024 12:06:46 +0000 Subject: [PATCH] docs: Include note on revoked privileges [skip pizza] --- doc/how-to/how-to-generate-a-secret.md | 2 +- doc/how-to/how-to-grant-metabase-permissions.md | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/how-to/how-to-generate-a-secret.md b/doc/how-to/how-to-generate-a-secret.md index c08ac8812f..afe1abea4a 100644 --- a/doc/how-to/how-to-generate-a-secret.md +++ b/doc/how-to/how-to-generate-a-secret.md @@ -1,4 +1,4 @@ -# How to generating a secret +# How to generate a secret ## Process 1. Generate a new secret using a random password generator, such as 1Password diff --git a/doc/how-to/how-to-grant-metabase-permissions.md b/doc/how-to/how-to-grant-metabase-permissions.md index 1cce89ccfa..7efae2cb17 100644 --- a/doc/how-to/how-to-grant-metabase-permissions.md +++ b/doc/how-to/how-to-grant-metabase-permissions.md @@ -52,3 +52,5 @@ When adding a new view, you will need to grant the `metabase_read_only` role `SE ```sql GRANT SELECT ON public.YOUR_NEW_VIEW TO metabase_read_only; ``` + +⚠️ Please note - when views are dropped and re-created, associated privileges are revoked. Be sure to re-grant `SELECT` permissions when updating views via Hasura migrations. \ No newline at end of file