The Site Pages Templates feature is useful. However, if you set any of the templates in the Site Pages\Templates folder to be read-only for a user they no longer see that template available on the +New menu when trying to create a new page such as a News Post.

Many of our users are modifying these templates when we don't want them to be able to.

We raised a premier support ticket with Microsoft and they reproduced this behaviour and advised that users must have contribute access to a template to be able to create page based on that template. Nuts right? They advised the only way they would fix this was if it was voted for by user voice. So please vote. We need 100 votes in 90 days to get them to respond.

In each library, there should be two kinds of versioning settings, each with its own settings for major and minor versions.

One kind of versioning settings for DOCX, XLSX and PPTX (i.e. file types with co-authoring and efficient shredded storage). In those versioning settings, the number of major versions can be higher (since less storage is used for each version).

Another kind of versioning settings for other file types (i.e. file types with less efficient shredded storage and no co-authoring). In those versioning settings, the number of major versions can be lower (since fewer version are probably needed and more storage is used for each version).

Co-authored Excel files often need 500 versions or more (for a few weeks protection).

A TIFF file in the same library certainly doesn't need 500 versions.

Don't tell us to store those files in separate libraries. It's not always convenient.

In SharePoint Online (and consequently in Teams), a lot of space is wasted on long version histories for files that can't be co-authored and don't need as many versions as files that can be co-authored (DOCX, XLSX and PPTX). To make matters worse, the file types that don't have co-authoring are the same file types that have less efficient shredded storage.

Two kinds of versioning settings in each library, please! One kind for DOCX, XLSX and PPTX (file types with co-authoring and efficient shredded storage). Another kind for the rest.

Hi There,

I have found the minimum width value for each column header, and especially the title column, to be much too high. We should be able to condense or stretch any column header width to ANY desired value and then save the view. Any meaning any.

SharePoint Lists' restriction on the range of widths allowed for a column header makes it incredibly difficult to promote using the product in our company. Which is in turn restricting our ability to embrace PowerApps and Power Automate.

To be clear:
This is for SharePoint on Outlook 365 with modern view.
I am not asking for column width to save with view. This has been implemented.
I am not asking how to change column width. I understand I can click and drag.
I know that column width can be changed using json in column format, but that only affects the child or the entries in the column, not the parent.

What I am asking for

Say, for example, you have a column header with 100 characters, but the data you are inputting is a single digit.
We should, if we wanted to, be able to reduce the header width to 1 character, and save the view.
We don't need a min of 20 characters, for instance. We know what we are doing.

Hope this was clear enough.

Best,
ThePeople

When adding a link to the Hero web part or the Quick links web part you cannot browse through the Site Pages library when selecting Sites. You might get lucky and find the page you want to link to in Recent but if not you are going to have to paste the link in the From a link area. I can browse other libraries to link to a document but I can't browse the Site Pages library to link to a page... WHY??

Microsoft why are you making it so difficult for users to add links to pages??

Please list the Site Pages library in Sites from these web parts.

Document templates can't be used from the 'new' button if a person isn't a member or visitor of a site even if a folder in the site is shared with edit rights to them.
You also can't change the rights on the hidden 'forms' folder where the templates get saved after uploading them via the 'new' button so you cannot resolve this, the user can however still see the 'template' in the new button, but clicking on it just takes you to an about:blank page.

You should be able to share a folder and allow someone to use the templates under the 'new' tab otherwise you're not able to fully collaborate and having solutions requiring you to have templates via the word app itself don't suffice.

Current situation:

It's not possible in SharePoint Online to display referenced items (e.g. linked documents or list items in the quick links web part or files in the file viewer web part) in the page details. Furthermore, it's not possible to show the usage of a page, file or list item in the details of an item. Usage is e.g. when an file stored in a document library is linked on a page(s) or in an list item.

Improvement:

Modern document management with SharePoint will be more efficient and would reach another level of maturity if the feature of page references and item usage would be implemented.

1. Display referenced items (e.g. linked documents or list items in quick links web parts or files in the file viewer web part) in the page details.

2. Show the usage of a file or list item in the details of an item.

3. Offer content life-cycle functionality - implement notifications for the last modifier of an page/item

--> The last modifier of a page should be notified if an referenced item on a page has been deleted or replaced (e.g. file, page, or list item)

Benefits:
- Full tracebility of all items in SharePoint to ensure a proper content life-cycle which will support the target of zero redundancy
- Content owner awarness of updated/deleted items which are used be multiple editors