Propose and review changes

Who can do this

Any member with the User role can propose changes. Approving a proposal: new notes and workflows need a Data Admin, or a workspace admin when the feature is workspace-scoped; new data apps need an Admin. Committing an edit draft (note, workflow, or table) needs a Data Admin. Nobody can approve their own proposal.

Changes to shared features by non-admins are staged, never direct. They come in two shapes:

• A proposal is a brand-new resource waiting to become shared — its Inbox row reads “proposed as a new shared workflow” (or note, or data app).
• An edit draft is your private copy of an existing shared resource. The live version is untouched until an admin commits your draft.

See Versions, drafts, and approvals for the full model.

As the requester

1. Make the change in chat. In a shared feature, Ronja files a non-admin’s new resources as proposals and their edits as drafts automatically. (Admins’ changes go live once they approve Ronja’s action in chat.)
2. Submit the draft when it’s ready: click Submit for review on the resource’s draft banner (workflows and data apps), or ask Ronja to submit it (notes). The chip flips from Draft to Review requested.
3. Track everything under Account → Requests — your proposed notes, workflows, and data apps, your open drafts, plus a Recent promotions history of settled scope-change requests.
4. Click Withdraw on any pending item you’ve changed your mind about.

Admins don’t see your draft at all until you submit it — and their Approve button won’t appear until you do.

As the reviewer

1. Open the Shared features page (/features).
2. Find the Inbox at the top of the page; narrow it with the Content filter pill to see proposals and drafts.

The Inbox: every proposal, draft, handover, and move waiting on a decision.

3. Click Review on a draft or handover row; click a proposal row itself to open the full review (or use its inline Approve / Reject).
4. Check the contents. Proposals show the full resource (“Review proposal”); drafts show a diff against the live version — workflow drafts add an AI-written Change summary, a metadata diff, an output preview, and the code diff.
5. Click Approve to commit — the change goes live and the previous version lands in version history — or Reject.

Caution

Approving publishes to everyone the feature is shared with, immediately. On table drafts, watch for the banner “Live has changed since this draft was created” — approving overwrites changes that landed after the draft forked.

Note

The Inbox is on the Shared features page — not the Governance page, which holds approval-policy settings. See Versions, drafts, and approvals for that distinction and the self-approval policy.