1
Feature Request: Shared Folder with Protection + Code Snippet History
Source: supabase/supabase#37973 · opened by @MAlMazrou
Note: Some aspects of this request have been raised in earlier discussions, but this proposal is intended as a broader, generalized enhancement that consolidates those ideas into a single feature set. 1. Summary Add the ability to create a shared folder within the Supabase project dashboard where team members can organize, store, and collaborate on shared assets (e.g., SQL snippets, policies, functions). 2.Requested Features 2.1.Shared Folder Creation -A dedicated "Shared" section inside the project. -Users can create subfolders for organizing assets. 2.2.Folder Protection -Option to lock or protect folders (e.g., require admin approval to modify or delete). -Role-based access (view-only, edit, admin). 2.3.Code Snippet History -Keep a version history of saved SQL/code snippets. -Allow rollback or view past changes. -Toggle option: users can enable/disable history based on preference. 3.Why This Matters -Teams often collaborate on SQL queries, pol…
No pledges yet. Be the first to back this.
Comments
Similar requests
Project Termination protection
2 votes · 0 comments
Delete Protection Feature
2 votes · 0 comments
Seed folder instead of / in addition to seed.sql file (backwards compatible)
2 votes · 0 comments
Should Supabase make PKCE optional for confidential clients in the OAuth server?
1 vote · 0 comments
Turnstile
2 votes · 0 comments
No comments yet.