Matthew Parowski

My feedback

  1. 4,127 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    441 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Matthew Parowski commented  · 

    Oh my goodness gracious yes. In my organization, it seems to be the most senior people who constantly try to reply to messages but spawn new threads. Politely correcting them doesn't fix their behavior either; the UI has to be improved. Maybe starting a new conversation could be a BUTTON rather than an all-too inviting TEXT BOX.

    Matthew Parowski supported this idea  · 
  2. 3,541 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    307 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This feature request is working its way through the backlog queue. No new details are available yet.

    -Warren

    Matthew Parowski commented  · 

    We were looking for a variation on Scenario A, since our concern is mainly about file storage. I can see this going two ways, and it would nice to have a choice: (A1) When creating a Team, point to an existing document library on an existing SharePoint site as the repository for "Files" associated with the Team, and let the Team use that in the way it uses SharePoint in the current architecture. If there are other (hidden) libraries or lists that need to be created to add a team, that's fine. (A2) When creating a Team, point to an existing Site and have the Team create everything it needs within that site, including the document library. It's fine if the Team creation process creates a new document library within the site for this purpose. Permission to the files (including the Team files) to be driven by the existing SharePoint site permissions structure; no need for the permissions to be driven by the Team membership.

    Q1: We have two use cases for different types of collaboration. In one of them (and the more urgent), it's fine if the channels continue to create folders within the "Files" space within the Document Library, but it would be nice to have the option to have files tied to different document libraries. In our other BYOS use case, we have existing sites with a lot of different document libraries, each of which have different permissions. In this case, what we would probably want to do is create a different Team associated with each Document Library (until Teams is able to manage permissions on Channels within the team). In both of these cases, permissions to the files should be driven by the permissions configured on the SharePoint site, since we generally want content on these sites to be searchable/discoverable by people outside of the Team proper.

    Q2: 9 - having Teams store files on a site with wider-access-than-the-Team-list permissions is critical to our corporate information security framework.

    Q3: Channels is much less of an issue for us than the default "Files".

    We are already experimenting with Scenario B as a workaround to our needs, linking to existing SharePoint document libraries as a "Tab", but the inability to remove the "Files" tab causes confusion for users.

    Matthew Parowski commented  · 

    My company provisions new SharePoint site collections (based on "SharePoint Team Sites"--not "Team SharePoint Sites") for each of our field offices using a standard set of 15 document libraries that are used to ensure that different categories of files are accessible to the right subsets of staff in each of our field offices. What we are looking for is the ability to add the Teams conversations/collaboration front-end to that existing SharePoint site collection. It would be fine if the Teams/Groups infrastructure also added a new document library for "Teams"-related files, but we have a governance structure around our SharePoint document libraries (15 of them) that we have a strong need to preserve. The single Teams site lacks sufficient corporate visibility or governance for our needs, but the collaboration features for the subset of staff who use a site are outstanding and in high demand. We are currently in a position where these groups are creating team sites on their own and then neglecting the governed SharePoint site, which creates huge audit and compliance liabilities for my company down the road, and/or a governance nightmare where we are constantly trying to force people to save files in one place and collaborate in another. The best work-around we have found so far is to create a Tab in Teams for the SharePoint site, which then shows up in an iFrame. This is tolerable, but a tighter integration would be so much more attractive.

    Matthew Parowski supported this idea  · 
  3. 415 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    217 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    Matthew Parowski supported this idea  · 
    Matthew Parowski commented  · 

    Glad you posted the solution; same thing happened to me. Very annoying. Teams should force sign-out when it hits this error.

Feedback and Knowledge Base