Permission & Access Issues

How to Fix SharePoint Site Creation Errors with Custom Permissions

Algirdas JasaitisAlgirdas Jasaitis Nov 3, 2026 868 views

Question details

Users encounter unexpected errors, incorrect file names, or extra blank pages when creating a SharePoint site or page using a custom permission group.

How to Fix SharePoint Site Creation Errors with Custom Permissions
Product
Microsoft SharePoint
Device & OS
not provided
Scenario
Creating a new site or page in SharePoint with customized user permissions instead of standard ones.
Observed behavior
The system generates an unexpected error, creates an additional blank page, or assigns a random file name (such as '1fvjfumm.aspx') instead of a file name matching the provided site title.
Before you start

Ensure you have the necessary administrative privileges to view and modify site permissions in SharePoint, or have the contact information for your organization's Microsoft 365 administrator ready.

Solution 1Recommended

Compare Custom Permissions with the Standard Contribute Level

Verify if the issue is tied to the custom permission group by temporarily assigning standard Contribute permissions, which include delete rights.

When users lack delete permissions in SharePoint, the site or page creation workflow can break, resulting in mismatched file titles or blank pages.

1
Access Site Permissions

Navigate to your SharePoint site, click on the Settings gear icon in the top right corner, and select 'Site permissions'.

2
Open Advanced Settings

Click on 'Advanced permissions settings' at the bottom of the panel to view the current permission levels assigned to your users.

3
Assign Standard Contribute Rights

Temporarily grant the affected user the standard 'Contribute' permission level to see if it resolves the creation error.

4
Test Page Creation

Ask the user to attempt creating the site or page again. If the site title and URL generate correctly (e.g., matching the intended title instead of random characters), the custom permission group is at fault.

5
Modify the Custom Group

Edit the custom permission group to include the necessary 'Delete Items' and 'Delete Versions' rights to prevent random file name generation.

Compare Custom Permissions with the Standard Contribute Level
InfoPath Warnings: Any InfoPath messages appearing during this process are typically irrelevant, as InfoPath might be the only default form-setting option shown for calendar lists even when disabled.
Free Microsoft Office alternative

Simplify Your Document Management with WPS Office

Dealing with complex SharePoint permissions and backend errors can slow down your team's productivity. Consider switching to WPS Office, a lightweight, user-friendly, and highly compatible alternative to Microsoft Office. It offers robust document collaboration features without the hassle of intricate administration, allowing you to focus on your actual work instead of troubleshooting IT issues.

Free and lightweight office suite with a clean, intuitive interface.Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Built-in cloud collaboration tools that are far simpler to manage than SharePoint.Seamless migration with no steep learning curve for your team.
microsoft office alternative - wps office

Frequently Asked Questions

Why does my new SharePoint page have a random file name like '1fvjfumm.aspx'?

This typically happens when the user creating the page is assigned to a custom permission group that lacks 'Delete' permissions. Without delete rights, SharePoint fails to correctly match the underlying file name to the site title you provide during creation.

Do I actually need delete permissions just to create a SharePoint page?

Yes, in many custom permission configurations, lacking the delete permission interrupts the standard page creation backend workflow, resulting in incorrect file names or unexpected blank pages being generated.

What should I do if the standard Contribute permission doesn't fix the issue?

If granting standard Contribute rights does not resolve the site creation errors, the problem is likely a backend tenant issue rather than a simple permission misconfiguration. You should contact your IT administrator to open a support ticket with Microsoft 365 support.