Hi @OESteve ,
I tested it and encountered the same situation as you. This is because Add and Customize Pages - Add, change, or delete HTML pages or Web Part Pages, and edit the Web site using a Microsoft SharePoint Foundation-compatible editor
is mainly for the page of Classic experience. It is useless for modern experience. Moreover, the page is also stored in the library and can be regarded as a file, that is, a special item. Therefore, as long as you check Add items
, this permission level can also add a page.
I have a workaround for your reference:
You first break the permission inheritance of the Site Pages library, and then grant these users the Read permission to the Site Pages library. In this way, the New
button in the Site Pages library will be removed.
Even if there is still an entrance to Add a page elsewhere, you will receive an Access Denied prompt when you click it.
At the same time, these users can view the pages in the Site Pages library.
For your references:
Good day!
If the answer is helpful, please click "Accept as Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.