A Thorough Comparison of Webflow Site Roles and Permissions: For Efficient Team Site Management

Site Settings

A Thorough Comparison of Webflow Site Roles and Permissions: For Efficient Team Site Management

Daisuke K

Marketer

公開日：

2026-05-11

更新日：

2026-05-13

Index

Introduction

Webflow is a popular platform for building high-quality websites without code. However, when operating as a team, it's crucial to clearly define "who can do what."
This article will clearly explain the differences between each role within Webflow's "Site Roles and Permissions."

‍

Reference:

https://help.webflow.com/hc/en-us/articles/41015796747667-Site-roles-and-permissions#h_01K3HMXMWDKZN1JCHKGRC7XDSA

‍

What are Site Roles?

Site Roles refer to the access levels granted to each member within a Webflow workspace.
To maintain site security and editing efficiency, Webflow primarily offers the following seven types of roles:

Site Manager
Designer
Limited Designer (Enterprise only)
Designer (Needs Approval) (Enterprise only)
Marketer
Content Editor
Reviewer

Features, Pricing, and Use Cases of Key Roles

Site Manager

Features: This role has the highest level of authority. Site Managers can perform all operations, including archiving sites, transferring them, managing plans, and creating API tokens.

Pricing: $45/seat/month (Full seat)

Permissions:

Can view all sites
Can manage workspace settings, teams, app development, and billing

Use Cases:

Project managers or team leaders
Individuals with final decision-making authority over the site
Administrators who manage billing and plan changes

Designer

Features: This role allows for free modification of a site's design and structure. Designers can access "Build Mode" and "Design Mode," and perform tasks such as creating/editing classes and components, and building CMS.

Pricing: $45/seat/month (Full seat)

Permissions:

Can design using all features

Use Cases:

Web designers or front-end developers
Team members responsible for site structure and design
Individuals responsible for creating new pages or components

Marketer

Features: This role is involved in SEO, A/B testing, and analytics settings. Marketers can use the Optimize feature (A/B test settings) and view analytics reports, making it ideal for marketing professionals.

Pricing: $19/seat/month (Limited seat)

Permissions:

Can build pages using components

Use Cases:

Marketing managers or SEO specialists
Team members responsible for A/B testing and conversion optimization
Individuals who propose site improvements based on analytics data

Content Editor

Features: This role accesses Webflow's CMS and is responsible for editing and publishing content. While they don't have site-wide publishing permissions, they can safely update articles and pages.

Pricing: $19/seat/month (Limited seat)

Permissions:

Can only edit content

Use Cases:

Writers responsible for blog posts or news
Individuals responsible for updating product information or company details
Team members responsible for regular content updates

Reviewer

Features: This role is dedicated solely to reviews. Reviewers cannot edit or publish, but can only comment and approve.

Pricing: $0/seat/month (Free seat)

Permissions:

Can only view the site and comment

Use Cases:

Clients or stakeholders
Internal quality control personnel
Individuals responsible for final checks

Permission Comparison

Summary: List by Key Features

We've summarized the main permissions for each role by feature:

機能カテゴリ	Site Manager	Designer	Marketer	Content Editor	Reviewer
サイト管理（移転・アーカイブ・請求）	✅ 全権限	❌	❌	❌	❌
デザイン・開発（デザインモード・コード・コンポーネント）	✅ 全権限	✅ 全権限	❌	❌	❌
コンテンツ管理（CMS・ページ編集・公開）	✅ 全権限	✅ 全権限	✅ 一部制限	✅ 一部制限	❌
マーケティング（A/Bテスト・分析・SEO）	✅ 全権限	✅ 全権限	✅ 全権限	✅ 一部制限	✅ 閲覧のみ
レビュー・承認（コメント・承認・プレビュー）	✅ 全権限	✅ 全権限	✅ 全権限	✅ 全権限	✅ 承認のみ

‍

Key Limitations:

Designer: Limited site management functions, requires administrator permission for publishing.
Marketer: Cannot edit design or code, but can edit CMS.
Content Editor: Cannot edit design or code, but can edit and publish content.
Reviewer: Cannot edit or publish, but can only comment and approve.

Details: Full List of Permissions by Feature

Below is a detailed comparison table of the permissions each role has:

▼ 各ロールの権限詳細を見る

権限	Site Manager	Designer	Limited Designer*	Designer (needs approval)*	Marketer	Content Editor	Reviewer
ワークスペース外へのサイト移転	✅	❌	❌	❌	❌	❌	❌
サイトのアーカイブ	✅	❌	❌	❌	❌	❌	❌
サイトプランと請求情報の購入・管理	✅	❌	❌	❌	❌	❌	❌
デザインモードへのアクセス	✅	✅	✅	✅ (ページブランチ上)	❌	❌	❌
ビルドモードへのアクセス	✅	✅	✅	✅	✅	❌	❌
エディターモードへのアクセス	❌	❌	❌	❌	❌	✅	❌
サイト共有用の読み取り専用リンク作成	✅	❌	❌	❌	❌	❌	❌
コンポーネントを使用したページの作成・編集	✅	✅	✅	✅	✅	❌	❌
新しいクラスの作成	✅	✅	✅	✅ (ブランチ上)	❌	❌	❌
新しいコンポーネントの作成	✅	✅	❌	❌	❌	❌	❌
既存のクラス、コンポーネント、変数の変更	✅	✅	❌	✅ (ブランチ上)	❌	❌	❌
既存コンポーネントをページスロットに追加	✅	✅	✅	✅ (ブランチ上)	✅	❌	❌
コンポーネントプロパティ値の編集	✅	✅	✅	✅ (ブランチ上)	✅	✅	❌
コレクションの作成・削除	✅	✅	✅	❌	❌	❌	❌
コレクションアイテムの作成、更新、削除、公開	✅	✅	✅	❌	✅	✅	❌
ページ設定の変更（パスワード保護、SEOタイトル、メタ説明など）	✅	✅	✅	✅ (ブランチ上)	✅	✅	❌
ページブランチの作成	✅	✅	✅	✅	✅	✅	❌
ページブランチのマージ	✅	✅	✅	✅ (承認が必要)	❌	❌	❌
ページブランチの編集	✅	✅	✅	✅	✅ (ビルドモード)	✅ (エディターモード)	❌
ライブサイトへの変更の公開	✅	✅ (Can publishが有効時)	❌	❌	✅ (Can publishが有効時)	✅ (Can publishが有効時)	❌
サイトアクティビティログの表示	✅	✅	✅	✅	✅	✅	❌
サイトのコードとしてエクスポート	✅	✅	✅	✅	❌	❌	❌
サイトのカスタムコードセクションへのアクセス	✅	✅	❌	❌	❌	❌	❌
サイト設定でのフォーム送信の表示・ダウンロード	✅	✅	✅	✅	✅	✅	❌
サイト用APIトークンの作成	✅	❌	❌	❌	❌	❌	❌
ライブラリの共有、インストール、管理	✅	✅	❌	❌	❌	❌	❌
共有ライブラリからのコンポーネントと変数の使用	✅	✅	✅	✅ (ブランチ上)	✅ (サイトで既に使用されている場合)	❌	❌
アプリのインストール・アンインストール	✅	✅	❌	❌	❌	❌	❌
レビューのリクエスト	✅	✅	✅	✅	✅	✅	❌
レビューの承認	✅	✅	❌	❌	❌	❌	✅
コメントの作成、表示、解決	✅	✅	✅	✅	✅	✅	✅
サイトのプレビュー	✅	✅	✅	✅	✅	✅	✅
OptimizeとAnalyzeトラッキング設定の変更	✅	❌	❌	❌	❌	❌	❌
Optimizeエクスペリエンスの作成・変更	✅	✅	✅	❌	✅	❌	❌
Optimizeイベント、オーディエンス、ゴールの作成・変更	✅	✅	✅	❌	✅	❌	❌
Optimizeバリエーションの作成・変更	✅	✅	✅	❌	✅	✅	❌
Optimizeバリエーション/エクスペリエンスの有効化・無効化	✅	✅	✅	❌	✅	✅	❌
アクティブまたは過去のOptimizeエクスペリエンスの結果表示	✅	✅	✅	❌	✅	✅	✅
アナリティクスレポートデータの表示	✅	✅	✅	❌	✅	✅	✅
GSAP Core、プラグイン、イーズの切り替え	✅	✅	❌	❌ (設定は表示可能だが変更不可)	❌ (設定は表示可能だが変更不可)	❌	❌
サイト設定 > カスタムコードでのデフォルトカスタムコードプレビュー切り替え設定の変更	✅	❌	❌	❌	❌	❌	❌
CMS編集アクセスの管理	✅	❌	❌	❌	❌	❌	❌

*Enterprise-only roles. If you previously used these roles as an Enterprise customer or partner, they will automatically be converted to custom roles. You can further customize them based on your team's needs.

By setting the optimal role according to each team member's responsibilities, you can prevent duplicate work and potential errors.

Best Practices for Team Operations

Limit "Site Manager" to the minimum number of people.
- Administrator privileges are powerful, but they also carry a high risk of errors, so grant them only to trusted personnel.
Divide work between designers and marketers.
- Separating design and marketing analysis tasks enables more efficient operations.
Grant "Content Editor" to content personnel.
- This allows for safe CMS operation and smooth progress with SEO and article updates.
Set "Reviewer" permissions for review personnel.
- This clarifies the approval workflow and maintains the quality of pre-publication checks.

Summary

Webflow's roles and permissions significantly impact the efficiency and security of team operations.
By clearly defining "who can do what" and appropriately dividing tasks, you will be able to build a smoother and more secure site management system.

‍

あなたのWebサイトにブーストを。

Booostはノーコードツール「Webflow」に特化したWeb制作サービスです。
デザイン・マーケティング・翻訳の3つの最適化で、Webサイトの集客力を最大化します。

制作実績を見るお問い合わせはこちら

この記事を監修した人

Daisuke K

Marketer

He joined IGNITE as CMO in 2021. Bringing prior experience in the marketing industry, he is now developing marketing strategies for international markets at IGNITE. He oversees B2B and B2C projects from various countries and regions, providing support to Japanese companies looking to expand overseas, as well as foreign companies aiming to enter the Japanese market.

A Thorough Comparison of Webflow Site Roles and Permissions: For Efficient Team Site Management

Index

Introduction

What are Site Roles?

Features, Pricing, and Use Cases of Key Roles

Site Manager

Designer

Marketer

Content Editor

Reviewer

Permission Comparison

Summary: List by Key Features

Details: Full List of Permissions by Feature

Best Practices for Team Operations

Summary

関連記事

Blog title heading will go here