Pedro RodriguesandClaude Opus 4.6
f7d2160e0c
### Summary - The `move` operation requires `select` + `update` permissions (not `select` + `insert` as previously documented). The implementation was changed in [supabase/storage#400](https://github.com/supabase/storage/pull/400) to update the row in-place instead of deleting and reinserting, but the docs were never updated to reflect this. - The `copy` operation requires `select` + `insert` by default. When the user also has `update` permission, the copy can be performed as an upsert, overwriting the destination if it already exists. - Added an `update` policy example alongside the existing `select` and `insert` examples. ### Related Fixes https://github.com/supabase/storage/issues/807 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Enhanced guidance for storage copy operations with clarified permissions requirements on source and destination. * Added upsert option details for users with update permissions. * Clarified move operation requirements for select and update permissions. * Updated policy examples with explicit operation names and owner authentication checks. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Reference Docs
Supabase Reference Docs
Maintainers
If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.
Versioning
All tools have versioned docs, which are kept in separate folders. For example, the CLI has the following folders and files:
cli: the "next" release.cli_spec: contains the DocSpec for the "next" release (see below).cli_versioned_docs: a version of the documentation for every release (including the most current version).cli_versioned_sidebars: a version of the sidebar for every release (including the most current version).
When you release a new version of a tool, you should also release a new version of the docs. You can do this via the command line. For example, if you just released the CLI version 1.0.1:
npm run cli:version 1.0.1
DocSpec
We use documentation specifications which can be used to generate human-readable docs.
- OpenAPI: for documenting API endpoints.
- SDKSpec (custom to Supabase): for SDKs and client libraries.
- ConfigSpec (custom to Supabase): for configuration options.
- CLISpec (custom to Supabase): for CLI commands and usage.
The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.
Contributing
To contribute to docs, see the developers' guide and contributing guide.