SharePoint sites vs. Site Collections - CONFUSED!
So, SharePoint sites vs. Site Collections has completely baffled me despite reading endless articles and watching many videos! As a very advanced end user, with very little admin. experience, I've recently been given the task of sorting out the existing O365 SharePoint sites / hierarchy in my new company *HURRAH*. However, I'm utterly confused! Here's what I know: All sites / sub-sites to date appear to have been setup in a single site collection (https://<mycompany>.sharepoint.com/) - I've checked this via SharePoint Admin Centre and SiteManager. All sites setup to previously appear to be 'old-style' team sites with 10 or so directly under the root (https://<mycompany>.sharepoint.com/<site name>/). There are then various levels of sub-site beneath these 10. When I go to the Office 365 home page (https://www.office.com/), click the SharePoint tile and then the '+ Create Site' button it unexpectedly appears to create a new Site Collection under https://<mycompany>.sharepoint.com/sites/<site name>/. If I go to the SharePoint Admin Centre and create a new site collection, it creates it under https://<mycompany>.sharepoint.com/sites/<site name>/. So, my questions are: When I go to O365 > SharePoint > '+ Create Site', is it creating a SharePoint Site Collection, just a Site or something else entirely (e.g. Site Collection with all the other new Groups functionality thrown in). If I'd like to create 3 'buckets' into which all new and existing content could be put, what should I be using (Site collections, Sites, Groups, something else ...)? The buckets I'd like are: Operations (for internal employee use only; with 3 subsites (e.g. Finance; HR; Marketing). Associates (for use by employees or external consultants who have been provided with an Office 365 account by my company; with no subsites). Projects (for sharing project documentation with external clients; with a separate site / subsite for each project). If I'd like to restructure all the existing sites (which are currently in a single site collection) so that they are in the 3 'buckets' above how do I best go about this? When I'm creating new 'sites', what should I be using?: Create Site option on SharePoint homepage. New > Site in SiteManager. Something else. I appreciate that this is a lot of questions, but I've done a lot of reading, watching videos and viewing webinars and I'm at a loss! Thanks in advance for any help you can provide! Oz
Understanding Groups vs Team Sites, need help
Hey everyone, I'm struggling to understand the differences between these two site types, as we are starting to roll out SPO through our organization. Just having a few questions before I write up our proposal to management Is there a difference between team sites and group sites going forward? Are groups just replacing teams? Is there a way to convert one to another? Is there a need to? Is there any method for creating Modern team sites or is there a difference between modern and "classic/2013 look and feel" sites? I found a number of articles about creating 'Modern' sites, but they are just creating group sites (like this using pnp powershell https://github.com/SharePoint/PnP-Guidance/blob/master/articles/modern-experience-customizations-provisioning-sites.md) This is what leaves me confused about the differences between the two. I'm hoping to use modern sites going forward, but don't want to roll out 2013 look/feel to users if something is going to change "soon", would rather just do it all at once. I'm feeling really confused and there is a lack of information that's easily available.
JSON list formatting to show/hide items based on SharePoint group membership
Hoping someone can confirm something for me. Here is the scenario: I have a SharePoint list with a 'Managers' column (type: Person/Group). I have created a SharePoint group called 'Managers SP Group'. I have created an Office 365 group called 'Managers'. I have added 'Managers' to the 'Managers SP Group'. The list is populated with items, and the 'Managers' column is populated with SharePoint groups e.g. 'Managers SP Group'. I want to create a custom view using JSON formatting that shows/hides items in the list based on whether the user viewing the list is a member of 'Managers SP Group' Question: a) Is this possible? b) If so, what is the JSON required? I know that if I used a person column populated with single users it is as follows: "display": "=if([$Managers.email] == me ,'','none') ...but I don't know what this would be for using a group. Hope someone can help! Thanks
Cannot provision SP modern site with Group programmatically - "Alias is already in use"
Hi, I'm building a solution that can provision O365 Groups with associated Modern Team Site and Teams. While trying to create some new Sites with Groups, sometimes the creation fails with the error message "The alias for the group already exists". Provisioning : Tried both using New-PnPSite from PnP PowerShell v2.28.1807.0 , as calling directly the REST API /_api/GroupSiteManager/CreateGroupEx with the same result (error) Payload: {"displayName":"TestPosh2", "alias":"13015", "isPublic":false, "optionalParams":{"Description":"","CreationOptions":{"results":[],"Classification":""}}} Response: {"error":{"code":"-2147024713, Microsoft.SharePoint.SPException","message":{"lang":"nl-NL","value":"De alias voor de groep bestaat al."}}} There isn't any visible existing Alias created in the tenant with that ID. To verify this I did check - Exchange Admin Center - Get-UnifiedGroup (Exchange) - Get-PnPUnifiedGroup - /_api/GroupSiteManager/GetValidSiteUrlFromAlias?alias='13015' They all return no matching data, the last one returns an OK status code with the available URL for site: http://tenant.sharepoint.com/sites/13015 How can I further see whether this alias can be in use, or successfully use it for the new site?
Breaking Inheriting Permissions and creating groups
Hello everyone, I am trying to control access to folders from specific user. So I created a library and "stopped inheriting permissions", my plan was to create groups with different access levels and add different users within. But as I was about to do this, I ran into an issue, I realized that groups are created at the site level and because of this, the groups will also have access to the other Libraries I have within the same site...which is something I do not want and is risky. The only option I see so far is to add individual users into the Library and then restrict each folder to each user individually. But the issue is that this will not work in the long run. Is there any other way to do this that anyone is aware of? Thank you all. The image below shows I am only able to a
Depreciation of 'Shared with us' on Group Sites
In leu of the latest update to the document library on groups sites showing 'In channels' and 'In site library' sections, the 'Shared with us' menu item that allowed you to locate any resources shared with the group centrally has been removed. After contacting Microsoft support, they indicated that this feature is being depreciated. There has been no admin notifications, timeline, or indication of how users are expected to locate resources shared with the group from the group context. My question is what next? It cant be logical to just drop a feature that supported collaborative working without a viable alternative. The expectation can't be to direct people to Onedrive to find these in the share section there...it defeats the concept of group-centric working and going to one place to locate everything to do with that group.
