Request a change vs Edit

On blog and other content lists, you may see Edit beside Request a change. They are different doors. Request a change only shows when Requests is entitled and turned on for that site.

Edit

Edit opens the content you already have: a post, a team member, a dish, a block of copy. You change the words and publish. No worker, no review card. Use this for everyday updates.

• Write or schedule a blog post.
• Change a name, photo, or title on Team.
• Update copy inside an existing page block.

Request a change

Use this when Edit cannot do it: a new layout, a bug, a page that is not in the editor, or behavior on the live site. It opens Requests compose and can seed the title and the public path (for example a blog post path or /team). Type and page chips start unset unless a page path was passed.

1. On a blog or content list, choose Request a change next to Edit.
2. Check the title and page. Add what you want changed.
3. Send. The Request lands on the board like any other.

When both show

If you do not see Request a change, the site does not have Requests access. Foundation and Advanced do not include it unless an operator granted an override, and Show Requests must be on. Edit still works.

Example prompts

• Edit: "Fix the spelling in last week's post."
• Request a change: "The contact form on /contact shows an error when I send."
• Request a change: "Add a second column of hours on the visit page."

Who can file

Owner and admin file and reply. Developers triage by hand or through a worker key. The list stays the same board for everyone. What you see on a thread is shaped by role.