Designers set the tone for the whole team

In Webflow, the Designer role carries the most access, and the most responsibility. Every structural decision a Designer makes ripples outward. A component built without props limits what a Marketer can do independently. A class changed without care cascades across the entire site. A page without slots means a Content editor is blocked before they've started.

That's why the Designer's role isn't just about building — it's about building for the whole team.

This section covers what Designers own in Webflow, how they collaborate with other Designers, and how their decisions create the foundation that everyone else works within. 

What Designers own

Designers are responsible for the parts of the site that affect everyone downstream:

• Structure and layout: how pages are built and organized
• The design system: classes, variables, and components that define the site's visual language
• Components and templates: the building blocks Marketers use to create pages
• Publishing permissions: who can publish what, and when

These aren't just technical responsibilities. They're collaboration responsibilities. The guardrails that Marketers and Content editors work within are only as strong as the systems Designers build and maintain.

Collaborating as a Designer

When multiple Designers are working on a site, Webflow supports real-time collaboration — meaning multiple team members can work simultaneously, seeing each other's changes as they happen. It's fast and immediate, ideal for low-risk updates, well-defined work, or situations where speed matters most.

For Enterprise teams that need more control, page branching takes collaboration a step further. Branching gives each Designer a separate copy of a page to work on independently, without affecting the main site or other teammates' work. When the work is ready, it gets staged, reviewed, and merged back in. It's slower by design — and that's the point. The next lesson walks through page branching and design approvals in detail.

Enterprise feature: Page branching & design approvals are available on Enterprise plans. See our pricing page to learn more about our plans.

Consider your own workflow

Before moving on, take a moment to think about how your team currently works:

• When Designers make changes, how often do those changes affect other people's work?
• Does your team have a shared understanding of when to work in real-time vs. when to branch?
• Are there parts of your site — shared components, key classes — that need more careful coordination?

You don't need answers to all of these yet. The next lessons will help you build that clarity.

Ready to dive in?

Now that we’ve covered the basics of the Designer role, let’s do a walkthrough of page branching and design approvals in Webflow.