diff --git a/docs/permissions/images/change-permissions.png b/docs/permissions/images/change-permissions.png index 7cedf72442d1508fea5451ce1421fa7600a91497..3c9f263caba46e47c42df62bb8d4672561ee0bf7 100644 Binary files a/docs/permissions/images/change-permissions.png and b/docs/permissions/images/change-permissions.png differ diff --git a/docs/questions/native-editor/sql-snippets.md b/docs/questions/native-editor/sql-snippets.md index 4604ed8e7d07ab14854697f6720bb476d44d2989..14cf8482ef3173cf4aba3e1158c077582a34efc5 100644 --- a/docs/questions/native-editor/sql-snippets.md +++ b/docs/questions/native-editor/sql-snippets.md @@ -95,7 +95,7 @@ Note: two snippets cannot share the same name, as even if a snippet is archived, Any user who has SQL editor permissions to at least one of your connected databases will be able to view the snippets sidebar, and will be able to create, edit, and archive or unarchive any and all snippets — even snippets intended to be used with databases the user lacks SQL editing access to. -Some plans contain additional functionality for organizing snippets into folders and setting permissions on those folders. See our [docs on SQL snippet folders and permissions](./sql-snippets.md). +Some plans contain additional functionality for organizing snippets into folders and setting permissions on those folders. See our [docs on SQL snippet folders and permissions](../../permissions/snippets.md). ## Learn more