SharePoint
Feedback by UserVoice

Anonymous

My feedback

  1. 1 vote

    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

    0 comments  ·  Sites and Collaboration » Web Parts  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  2. 1,961 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

    142 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 292 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

    32 comments  ·  Sites and Collaboration » Communication Sites  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Please work to remove the restriction that a site must be group-enabled in order to take advantage of Connector webparts such as to display an RSS feed

    Anonymous supported this idea  · 
  4. 9 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

    1 comment  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Enable Connector webpart for Modern Pages outside of group-enabled sites. Especially RSS feeds

    Anonymous supported this idea  · 
  5. 3,142 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

    246 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    This is a significant bug (inconvenience if you prefer) with obvious implications the longer a Teams channel has been utilized.

    1. Renaming the channel without renaming the back-end folder creates user confusion
    2. Renaming the back-end folder breaks the link and browsing files is no longer possible

    There needs to be either an "Owner" capability to repair or choose a specific folder to assign to the Files tab
    AND/OR
    There needs to be a GUID or other property that marks a folder with it's appropriate channel such that renaming on either end does not impact the association

    Anonymous supported this idea  · 
  6. 70 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

    4 comments  ·  Sites and Collaboration » Publishing  ·  Flag idea as inappropriate…  ·  Admin →
  7. 40 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

    1 comment  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →
  8. 123 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

    7 comments  ·  Sites and Collaboration » Communication Sites  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  9. 186 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

    6 comments  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  10. 6 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

    0 comments  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  11. 1,886 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

    329 comments  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →

    In modern pages, we open links within SharePoint in the same tab by default, and external links in a new tab. In the text web part, users can specify to open links in a new tab, but that isn’t the default behavior. Similarly, for navigation links, they follow the same rule (within SharePoint, same tab, external to SharePoint in a new tab). This is true of the modern web parts that support linking as well (hero, quick links, images, etc.) This is the pattern we’ve adopted for consistency.

    After reviewing other areas of modern sites, like the site pages library, document libraries, lists, site contents, etc. we did find some different opening behaviors which we’ll review and resolve.

    Can you help us understand if this pattern isn’t meeting your expectation, if we have some inconsistencies within modern pages we’ve missed, or if it’s the other areas of modern sites where…

    Anonymous supported this idea  · 

Feedback and Knowledge Base