Which Webflow role should monthly support use?

Match the role to the written request

A Webflow site role is the permission on that site. It is separate from the Workspace role, which decides which site roles a person can be given. The monthly request should name the work. The role should be the narrowest one that can actually do that work.

The plan is $999 per month and includes 10 hours of Webflow work. Additional work is $75 per hour. Before work exceeds the included hours, I share a written estimate and ask for your written approval. Additional work starts only after you approve it.

Your Webflow subscription, hosting, domains, and third-party apps stay in your own accounts and at your own cost. Give access with the permissions the work needs.

Example: the request is 'Add one shared class so the three pricing cards match, and update the footer script that prints the year.' A content editor cannot do either part. A Designer can. If the same request also needs a backup or a change to site billing, a Site manager is the role with those settings.

Use Designer access for layout and code

A Designer has full Designer features. That includes creating classes, creating components, changing existing classes, components, and variables, and opening the site's custom code. A Designer can also create and delete Collections, and create, update, delete, and publish Collection items.

A Site manager can design with those same Designer features. A Site manager can also manage site settings: backups, the Site plan and billing, transferring the site out of the Workspace, and creating an API token. Only a Site manager can access site backups.

On Growth, Agency, and Enterprise Workspace plans, Workspace admins and Site managers can change a person's site role from Site settings, Site access. Pick Designer when the written work is layout, new classes, components, or custom code, and the person does not need to manage billing or backups. Pick Site manager when the work includes those site settings.

A marketer can create and edit pages with components that already exist. A marketer cannot create new classes. If the request needs a new class, a marketer seat will stop at that class. Send the page-building work to a marketer only when the components already on the site are enough.

Keep a content editor on copy and CMS items

A content editor can edit content, edit component property values, edit global content inside components, and create, update, delete, and publish Collection items. A content editor can also change page settings, such as an SEO title, a meta description, or page password protection.

A content editor cannot use full Designer features, cannot build pages, cannot create classes, and cannot open custom code. The content editor guide is how to send that invite when the work really is copy and existing items. The team edits guide is which of those edits your own team can keep. This page is the role for the person doing the monthly request.

Example: 'Replace the first paragraph on /pricing with the attached sentence, and update the price on the existing Pro item.' That work fits a content editor. You do not need to hand over Designer access for a sentence and an item you already have.

A reviewer is narrower still. A reviewer can view the site and comment. A reviewer cannot publish. Reviewers cannot comment on components, on Collection items in the CMS panel, or on elements that are only visible through custom code or animations. A comment-only seat is not enough for a request that changes the page.

Treat publish as its own switch

Editing and publishing are not the same permission. On Growth and Agency plans, Can publish can be turned on or off for roles that allow it. A Designer, a marketer, or a content editor publishes the site only when Can publish is on.

You cannot change publish permission for a Site manager or a reviewer. A Site manager can publish. A reviewer cannot. Someone who is blocked from publishing the whole site can still publish individual Collection items that do not affect designs in progress. If that is more than you want, say so in the written note: new items stay in draft until you say to publish them.

Send the access note in writing

Communication is asynchronous and written only. There are no calls or meetings to decide the seat. In the same thread as the request, name the site, the role, and whether Can publish should be on.

Example: 'Invite the monthly support address to the marketing site as a Designer. Leave Can publish off. The first request is the pricing-card class and the footer script. I will reply in writing before anything goes to the custom domain.'

Urgent requests are reviewed and picked up within 24 hours. Other requests are reviewed and picked up within 48 hours. Those windows are pickup times, not a finish date, and not a reason to grant a wider role than the work needs.

Unused hours expire at the end of each monthly billing period and do not carry over. Memberships cannot be paused. You can cancel before the next renewal to stop future billing. Service continues through the paid period, and remaining included hours stay available until that period ends. A new website or a full redesign is a separate project.

The Webflow retainer is the plan this role decision belongs to. The retainer guide explains which ongoing work the included hours cover. Use this page when you are about to send an invite and you need the role to match the request.