Today a Dive can be viewed by the org, but only the owner can change its content. MCP (edit_dive_content / update_dive) and SQL (MD_UPDATE_DIVE_CONTENT) both fail with “Only the Dive owner can update its content.” Sharing is read-only.

Please add editor access, distinct from viewer:

Owner can grant named users, roles, or a service account edit on a Dive (content + new versions), without transferring ownership.

MCP and SQL writes succeed for anyone with editor (or owner) on that Dive.

list_dives includes Dives the caller can edit, not only ones they own.

Optional: org-admin or a “Dive editors” role that can edit any org-shared Dive.

Why it matters

We lint MotherDuck Dives from a shared service token and apply reviewer-approved content fixes. Reads work on org-shared Dives; applies fail unless the token owns the Dive. That forces us to either transfer/recreate every human-authored Dive under a service account, or have the owner paste SQL by hand.

Same bottleneck as this thread: CEO/analyst owns the dashboard, engineering/CI needs to edit it. Git-as-code helps only after everything is owned by one service account, which breaks “the person who built it still owns it.”

What we would use

Keep ownership with the author. Grant our lint/CI service account editor. Viewers stay read-only. Version history and MD_UPDATE_DIVE_CONTENT stay as they are; only the ACL changes.