Skip to content

Commit b14ec0f

Browse files
Merge pull request SharePoint#5791 from kaarins/patch-1
Update modern-experience-customizations-customize-pages.md
2 parents be40e63 + defd343 commit b14ec0f

File tree

1 file changed

+2
-9
lines changed

1 file changed

+2
-9
lines changed

docs/solution-guidance/modern-experience-customizations-customize-pages.md

Lines changed: 2 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Customizing "modern" site pages
33
description: Use custom branding in SharePoint Online, add "modern" pages programmatically, and add, delete, or update client-side web parts on "modern" pages.
4-
ms.date: 05/20/2020
4+
ms.date: 05/29/2020
55
localization_priority: Priority
66
---
77

@@ -68,15 +68,8 @@ You have multiple options to control whether the "modern" or "classic" page expe
6868

6969
### Tenant level configuration
7070

71-
If you want to completely disable the "modern" experience, it's best to use the tenant setting for this. Go to your tenant admin center (for example, contoso-admin.sharepoint.com), go to Settings, and select the "classic" experience.
71+
If you want to prevent users from creating new modern pages on all sites that don't already have modern pages, you can use the tenant-level setting in the new SharePoint admin center. Go to the [Settings page](https://admin.microsoft.com/sharepoint?page=settings&modern=true), select **Pages**, and then clear **Allow users to create new modern pages**. For more info, see [Allow users to create modern pages](/sharepoint/let-users-create-modern-site-pages).
7272

73-
**Site Pages section in the SharePoint tenant scoped settings in Admin UI**
74-
75-
![Site Pages section in the SharePoint tenant scoped settings in Admin UI](media/modern-experiences/site-pages-setting-admin-ui.png)
76-
77-
> [!NOTE]
78-
> - The tenant level setting can be a little confusing; **Prevent users from creating Site Pages** actually brings back the "classic" experience.
79-
> - The current configuration is cached, and signing off the session immediately shows the effect of this change.
8073

8174
### Web level configuration
8275

0 commit comments

Comments
 (0)