Modern Page Does Not Publish for Site Members: Fix
🔍 WiseChecker

Modern Page Does Not Publish for Site Members: Fix

When site members in a SharePoint communication site try to publish a modern page, they may see the Publish button grayed out or receive an error message instead of the expected confirmation. This problem occurs because the default permissions for members on a communication site do not include the Contribute permission level needed to publish pages. This article explains why the Publish button is disabled for members and provides the exact steps to grant members the ability to publish pages in a SharePoint communication site.

Key Takeaways: Fixing Publish Button for Site Members

  • Site permissions > Members group: Members of a communication site have Read permission by default, which blocks page publishing.
  • Change group permissions to Edit: Editing the permissions of the Members SharePoint group to the Edit permission level resolves the gray Publish button.
  • SharePoint admin center > Site permissions: Site owners can manage permission levels directly from the site without needing global admin rights.

ADVERTISEMENT

Why Site Members Cannot Publish Modern Pages

SharePoint communication sites are built for broad content broadcasting, not collaborative editing. When you add a member to a communication site, SharePoint assigns them the Read permission level by default on the site itself. The Read level lets a user view pages and files but not edit or publish them. The Publish button is tied to the Contribute or Edit permission level. Without at least Contribute, the button remains disabled for the member.

This design is intentional. Communication sites use the Site Members SharePoint group differently than team sites. On a team site, members automatically get Edit permission. On a communication site, members only get Read. To allow publishing, the site owner must manually change the permission level of the Members group from Read to Edit. The Edit permission level includes the ability to add, edit, and delete pages, which includes the publish action.

There is also a common misunderstanding about the Pages library itself. Even if a member has Edit permission on the site, the Pages library might have unique permissions that block publishing. In most out-of-the-box communication sites, the Pages library inherits permissions from the site. But if an owner has broken inheritance on the library, the member may still be blocked. The fix in this article assumes the library inherits site permissions, which is the default.

Steps to Grant Publish Permission to Site Members

Follow these steps to change the permission level of the Members group on a communication site. You must be a Site Owner or have Full Control permission on the site.

  1. Open the site permissions page
    Navigate to your communication site. Select the gear icon in the top right corner, then choose Site permissions from the menu. This opens the permissions panel on the right side of the screen.
  2. Access advanced permission settings
    In the permissions panel, select the link labeled Advanced permissions settings. This opens the classic permissions page in a new tab.
  3. Locate the Members group
    On the classic permissions page, you see a list of groups and users. Find the group named <Site Name> Members. For example, if your site is called Sales Portal, the group is Sales Portal Members.
  4. Edit the group permissions
    Select the checkbox next to the Members group name. On the ribbon at the top, select Edit User Permissions. A dialog box opens showing the current permission level.
  5. Change permission level to Edit
    In the dialog, uncheck the Read permission level. Then check the Edit permission level. Select OK to save the change. The Members group now has Edit permission on the site.
  6. Verify the fix
    Ask a site member to refresh the site page and open any modern page in edit mode. The Publish button should now be active. The member can make changes and publish the page.

ADVERTISEMENT

If the Publish Button Still Does Not Appear

Pages Library Has Unique Permissions

If the Publish button remains disabled after changing the Members group permission, the Pages library may have broken inheritance. To check this, go to Site contents and open the Site Pages library. Select the gear icon, then Library settings. Under Permissions and Management, select Permissions for this document library. If you see the message This library has unique permissions, the library does not inherit from the site. You must either restore inheritance or add the Members group directly to the library with Edit permission.

Member Is Part of a Different Group

Sometimes a user is added to the site through a different group, such as the Visitors group or a custom group with Read permission. Check which groups the member belongs to. On the classic permissions page, you can select a user name to see their group memberships. If they are only in the Visitors group, move them to the Members group or grant Edit permission directly.

Approval Workflow Blocks Publishing

If the site uses a page approval workflow, members may be able to submit pages for approval but not publish directly. This is a content approval setting in the Pages library. To check, go to Library settings > Versioning settings. Under Content Approval, if Require content approval for submitted items is set to Yes, members with Edit permission can only submit drafts. Only approvers can publish. In this case, add the member to the Approvers group or disable content approval.

Read vs Edit Permission: Key Differences for Page Publishing

Item Read Permission Edit Permission
View pages Yes Yes
Edit page content No Yes
Publish a page No Yes
Delete a page No Yes
Add web parts No Yes
Change page layout No Yes

After changing the Members group permission to Edit, site members can publish modern pages in a communication site. The key setting is the permission level assigned to the SharePoint group, not the Microsoft 365 group. Always verify the Pages library inheritance if the fix does not work. For sites that require content approval, remember that Edit permission alone does not bypass approval workflows. You must configure the approval group separately.

ADVERTISEMENT