Which Webflow edits should my team keep?

Keep the copy your role can already change

A content editor can edit content on the site. That includes the words in a heading or a paragraph, the values of component properties, and global content inside a component. If the sentence is wrong and the layout can stay, your team should change it. Sending a typo out spends the month on work an editor can finish.

Example: the homepage button says 'Book a call' and the approved line is 'Write to us'. A content editor can replace that sentence. The button style, the spacing, and the form do not need to change. That edit stays with your team.

Page settings sit in the same group. A content editor can edit the SEO title and the meta description. A wording fix in those fields does not need a designer. The editor access guide shows how to invite that person and how to leave design tools off.

A marketer's role is wider than a content editor's, and it is still not the full Designer. Read the next sections before you assume a marketer should send every page change out.

Leave Collection items in-house

A content editor and a marketer can create, update, delete, and publish Collection items. A blog post, a job listing, or a case study that uses fields you already have is team work. Publish the item when the copy is final. The CMS updates guide is a useful brief when someone else will enter the item for you, which should be rare if an editor already has access.

Creating or deleting a Collection is a different job. A content editor cannot do it, and a marketer cannot do it. A site manager or a designer can. A new field, a new template layout, or a Collection that does not exist yet belongs in the written queue.

Example: adding 'March office hours' as an item in the Events collection you already have is yours. Adding a speaker photo field, then changing the event template to show it, is not. The item can wait until the field exists. Do not ask an editor to paste the photo into the rich text as a workaround, because the next event will need the same workaround.

Someone who cannot publish the whole site can still publish an individual CMS item. A content editor does not need site-wide publish permission to put one finished item live. Can publish is a separate switch, and it lets that person publish the whole site. Leave it off when you want content edits without pushing every Designer change live.

Send new classes, new layout, and custom code

Full Designer features, new classes, and the site's custom code are outside a content editor's role. A marketer can create and edit pages with components that already exist, and can edit component property values. A marketer cannot create a new class or open custom code.

Send the request when the page needs something the current components do not include.

• A new section that needs its own layout and its own classes.
• A form change, such as a new field, a new notification address, or a success state with a different structure.
• An interaction, or custom code in the head or footer.
• A new page that cannot be assembled from components you already have.

Example: three pricing cards that do not exist as a component, with a new class for the highlighted card, belong in the queue. Changing the price text inside a card component you already use belongs with your team. If you are unsure, ask whether a new class is required. A yes means it goes in the queue. A no means an editor or a marketer can try it first.

Put only the outside work in one note

Do the in-house edits before you write the queue. Then send what is left: the page, the outcome, and what done looks like. Attach the final copy and the final image files. A sentence such as 'Add a three-card pricing row under the intro on /pricing, using the attached prices, and match the spacing of the card row on /services' can be picked up. 'Refresh the pricing page' cannot, because it mixes a text change your team can do with a layout nobody has described.

Keep one thread. If a teammate notices a typo while the layout request is open, fix the typo in the Editor, or add one line to the same thread if it truly needs a designer. A second channel that says 'also change the footer' is how a small edit gets lost, or how it gets done twice.

Save the month for the work your team cannot finish

The included hours go further when copy and existing CMS items stay with the people who already have the role for them. The Webflow retainer is the monthly plan for the work that is left, on a site you already have. The retainer guide describes that scope.

Send one written queue for the layout, the new classes, and the custom code. Communication is written only. There are no calls or meetings to sort which edit belongs to whom. The role list above is the sort.