Forum Discussion
ROLLING OUT: SharePoint Online team sites + Office 365 Groups & Pages
Tejas MehtaMicrosoft
SharePoint does provide the ability for Site Owners to specify different permissions on resources. Office 365 Groups promises a permission model whereby all group members have access to the group’s resources across workloads (e.g. conversations, files, notebook, etc.). To deliver consistency, SharePoint site collections associated with a Group will also follow this model. So, a group (site) owner can add new permission levels and assign to new users or groups on a resource, but would not be able to remove the permission levels assigned to the group’s owners or members. We are working on delivering a new permissions management UX that will allow for group (site) owners to change the group members’ permission level from Edit to Read-only (and vice versa) but you would not be able to remove the members from resources in the SharePoint site collection.
Having the ability to assign read-only access is a big deal in our case and I believe many others. As much we try to be more inclusive instead of exclusive, everyone having the same access doesn't always sit right. Often we say "teams" but within those teams are different roles, responsiblities and tasks. Sometimes that team isn't always about working together on every part but more about presenting final data/assets/reports/documents/etc to others. That collateral ultimately we want to surface through the teamsite/page itself.
I really think one of the biggest issues some of us struggle with is that Groups give us great tools for the "doing" and "working on it" modes and then teamsites let us finish everything off with the "presentation" piece. The issue is that we don't always want to expose the "working" pieces to everyone. Not everyone needs to see the cake being made in the bakery, or the discussions/disagreements/chaos in the background. Teamsites are like that glass window where the cake is shown. That's the struggle most of us have is that with Groups + Teamsites, now everyone can go into the back room.
- Only from what I understand, permissions for a Group's Site (Team Site) can be set independently from other aspects of the Group? The same is true for Files (Document Library)? There's of course every chance I've misunderstood!
- It follows the membership management Office 365 Groups offers. AKA, Office 365 Groups, the list of members, provides the authentication mechanism for these team sites; not the site settings > people and groups of SharePoint.
Joe Fedorowicz Office 365 Groups was always based on SharePoint Site Collection (i.e. top level site with one library).
The integration now expands this site into a full-blown SharePoint site as we know it. Therefore, more site ownership controls such as permissions and create other business apps, etc.
Yep, but we are now adding "Group Managers" into the mix. Are they going to live in the "Site Owners" by default? or will they just be members with permissions on the "Group" level?
Joe Fedorowicz currently the permission groups consist of owners, members and visitors. For each of the group, the group name permission object (i.e. test 3) resides in all of the above permission groups - screenshot below.
Makes perfect sense to use at least the owners and members group. We'll have await further information as how this will pan out.
- Can an O365 group be deleted and leave the SharePoint site intact?
And vice versa, can the SharePoint site be deleted and leave the O365 Group intact?
I'd really like to see something where you can enable/disable features in an Group/SharePoint site
e.g.
- I want JUST a sharepoint site with no group
- I want a group with no sharepoint site, and planner, and discussion turned on
- I want a group with a sharepoint site
- I want a group with planner turned off, and everything else turned off, just the discussion and document library
etc- Tejas Mehta
Hi Brent,
Office 365 Groups weren't designed to have workload components removed, and as such you cannot keep the an orphaned SharePoint site after removing its parent Group (or vice versa). There will still be ways to provision traditional SharePoint sites that are not connected to groups though.
Can you comment further on the scenarios where you would want to have stripped down functionality (e.g. just conversations and files)?
