SharePoint Online Document Libraries are missing possibly the two most basic and fundamental functions in the online portal:

- A move/cut function, which is missing altogether, both for folders and files
- A copy function, which although technically exists, is really over complicated for a function which has existed in a much simpler form in every document repository technology since the mid-1980s...

Currently, in order to move a file or folder from within the online portal between different libraries or even different folders within the same library...well the function just doesn't exist. So users need to either sync the site just to simply MOVE something or they need to Open in Explorer (and we all know how badly and slowly that works).

Secondly, in order to copy a file from within the online portal between different libraries or even different folders within the same library, I need to copy the URL of the target folder preemptively, then paste in the copy dialog box...should this be the procedure for simply copy/pasting something? Oh and that function's missing for folders...

So again users need to sync a site library or Open with Explorer just to simply copy paste something easily.

How does a document library product make it into production for years on end without having proper move/copy functionality? How does it even make it out of approval?

Three requested updates to significantly improve the Access Request process:

1) Allow multiple users to receive access requests

Access requests (Site Settings > Site Permission > Access Request Settings) can be sent to anyone with an email address, but it has three critical downsides: 1) you are limited to one email recipient; 2) the field does not accept SharePoint groups; and 3) it’s prone to misspellings of email addresses since the field is not a people picker.

One of the most extreme examples of how this is broken: My company’s CEO needs access to a file s/he has a link to, which s/he is going to display at the board of directors meeting in 15 minutes. The site owner forgot to give access or didn’t realize the CEO lacks access. The CEO requests access after clicking the link. The creator of the site has left the company. The request email gets lost in Exchange somewhere. No one knows the CEO is in need of access and the CEO is unable to present the document to the board of directors. Everyone looks a fool.
The best fix for this is to: a) use the site’s Owners group as the default recipients to start; b) allow for multiple email recipients as a people picker; and c) continue accepting an outside email address for those who have grown used to it.

From what I can tell, this is the only place in SharePoint where I'm limited to one individual and no ability to call out SP groups. The entire point of groups is to ensure permissions and communications work correctly based on a global change at the group level, which keeps things moving smoothly.

2) Display site owners on “Request Access” page

Display the names of the members of the Access Request group on the “Request Access” page so users have context to what they’re seeing, not just a blank box asking them to demand access.

3) Make “Request Access” page customizable

Allow for the “Request Access” page to be configurable by the Access Request group so there’s more context for users. For example, “Please do not contact IT with this request; only the site owners can provide access. Contact them directly if necessary.”

The Script Editor Web Part has been replaced by the Content Editor (which does a very limited iframe) and the new SPFX stuff. I am not a developer, but knowledgeable in HTML, Javascript, CSS. The SEWP met some very complex use cases (targeted for replacement by SPFX), but also some very simple use cases.

Example: Insert a formatted single HTML button, something that is big, draws attention, and encourages the user to click it to start an action.

What might be just 2 lines of code, has now turned into (what looks like) hundreds of files of deployment, installing all kinds of tools that I have never heard of or know what they are actually doing in the background.

I am finding SPFX to be specifically geared toward professional developers and limiting "citizen" developers from adding just simple things to SharePoint pages. I am trying to learn it, but there are so many things above my head at this point, and my role is not to be a full-time developer.

This is to lobby to bring back the Script Editor Web Part to meet simple use cases