SharePoint
Feedback by UserVoice

Sites and Collaboration

Welcome! This is your place to suggest ideas or vote for ideas for improving the SharePoint Sites and Collaboration experience.

How to submit a new idea

  1. Check if it's already been suggested. If it has, vote for it.
  2. If it's new, submit it in 50 words or less.
  3. Gather support!
  4. If your idea receives over 100 votes in 90 days, we will respond.
    If not, we will close it.

Want to engage further? Please visit the SharePoint Community

Note: we have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Bring Back Script Editor Web Part in "Modern" SharePoint

    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…

    759 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    44 comments  ·  Web Parts  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your suggestion.

    We do not intend to bring back a way to create or add ungoverned code on modern SharePoint pages. Therefore there won’t be any modern version of the script editor web part shipped from Microsoft. There are open-source solutions available that enable ungoverned code to run on select sites where it is installed, but those are not recommended or endorsed by Microsoft.

    The purpose behind the SharePoint Framework is to enable governance over all scripting solutions leveraged on SharePoint pages. This allows a SharePoint admin to disable a particular solution from all sites, immediately, from within the App Catalog. This centralized governance was not available when ad-hoc scripting was available in the site level only with page editing permissions, which caused potential security challenges.

    Please see this info about Getting Started with SPFx: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-developer-tenant

    If you do have specific scenarios (e.g. adding a call to…

  • Don't see your idea?

Feedback and Knowledge Base