內容簡介
Multigovernance 外掛為 WordPress 提供多用戶角色的區塊和設定權限管理，讓不同角色的用戶能夠根據需求編輯內容，避免不必要的誤操作，提升編輯效率和安全性。
【主要功能】
• 角色基礎的區塊可見性：根據用戶角色顯示或隱藏區塊
• 區塊設定控制：限制特定角色對區塊進階設定的訪問
• 支援所有區塊：兼容 WordPress 核心區塊及自訂區塊
• 針對角色的編輯器設計：為不同角色提供專注的編輯體驗
• 防止發佈錯誤：限制非技術用戶對關鍵區塊的訪問
• 無前端影響：所有限制僅適用於 Gutenberg 編輯器內部
外掛標籤
開發者團隊
② 後台搜尋「Multigovernance — Multi-user site, role-based permissions for blocks and settings」→ 直接安裝（推薦）
原文外掛簡介
When multiple people edit your WordPress site, not everyone should have access to the same blocks and settings. A contributor shouldn’t be able to touch layout blocks. An author shouldn’t be able to alter custom block configurations that affect the entire site.
Multigovernance gives administrators granular, role-based control over which Gutenberg blocks are visible — and which settings within those blocks are accessible — for every user role on your site.
The result is a cleaner editing experience for each user and fewer accidental misconfigurations for you to fix.
Key Features:
Role-Based Block Visibility: Show or hide any Gutenberg block based on user role. Editors see what they need — nothing more, nothing less.
Block Settings Control: Grant access to a block while restricting its advanced settings for specific roles, preventing configuration changes without removing the block entirely.
Works With All Blocks: Supports all default WordPress core blocks and any custom or third-party blocks installed on your site.
Tailored Editor Per Role: Create a focused, distraction-free editing experience for contributors, authors, editors, and any custom role you’ve defined.
Prevent Publishing Errors: Limit access to layout-critical or design-sensitive blocks so non-technical users can’t break the structure of your pages.
No Front-End Impact: All restrictions apply only inside the Gutenberg editor. Your published content and front-end output are never affected.
Govern your block editor. Protect your publishing workflow. Free with Multigovernance.
Who Is Multigovernance For?
Editorial & Publishing Sites — Control what contributors, authors, and editors can access in the block editor without overlap.
Agencies & Freelancers — Lock down advanced block settings before handing a site off to a client.
Corporate & Enterprise Teams — Give each department access to only the blocks relevant to their workflow.
Education & eLearning Platforms — Separate block access for instructors, students, and admins on the same install.
Membership & Community Sites — Match block access to membership tier so each user level gets the right editing tools.
Healthcare & Regulated Industries — Prevent unauthorized content changes where accuracy and compliance are critical.
WordPress Multisite Networks — Manage editorial permissions across multiple subsites with different teams.
Why Choose Multigovernance?
The Right Blocks for the Right People
Every role on your site has different needs. Multigovernance lets you match the editing interface to the user, so contributors aren’t overwhelmed, and admins aren’t cleaning up after accidental changes.
Settings Control Without Block Removal
Sometimes a user needs a block but shouldn’t touch its advanced options. Multigovernance lets you separate block access from settings access, giving you finer control than simply hiding the block entirely.
Works on Every Block You Use
Whether you’re using core WordPress blocks, WooCommerce blocks, or custom blocks from your theme or plugins, Multigovernance applies role-based rules across your entire block library.
Cleaner Workflow, Fewer Errors
A governed editor means fewer support tickets, fewer broken layouts, and faster publishing — because each user only interacts with what’s relevant to their role.
License
This plugin is licensed under the GPLv3 license. Please see the license file for more details.
Credits
MD Governance is developed by Multidots.
Explore Our Other Plugins
Multipasskey — Deploy enterprise-level, passwordless security
Multipress — Centralized publishing with controlled local edits for enterprise, departmental, or regional sites.
Multisync — Sync external data to custom fields to turn static sites into dynamic hubs.
