Forum Discussion
How to make my top level root site a "Modern team site"?
Hello,
I'm working on a pilot/proof of concept for one of my clients in Office 365. They had an old school team site with some old demo data on the root of their site. I wanted to start from a clean slate so I deleted the default site collection and created a new one. I expected to see the options to create a new modern team but instead it says it's an old "classic experience" team site.
So do I just ignore this top level classic team site and pretend it doesn't exist? Then I would just hit "Create Site" and make my new modern site and move forward with that? I guess I could remove the old classic empty "team site" from the Featured Links list, etc?
But then there is the issue of http://companyname.sharepoint.com taking you to the old empty team site. Was hoping to avoid that.
Or is there some way to make that top level root site a modern team site?
Thanks for any recommendations!
Jason Hartman
I had the same initial question as in this thread which was what to do about my tenant root site being on the classic template.
I wanted to use the hub site feature and it was recommended that I select a communication site or a team site that uses the modern template to create my hub site, so I created a communication site and then had a friend use Powershell to turn that site it into a hub site. Now I have about 20 different site collections for different projects and corporate functions and they are all associated with that hub site. It is all working fine except for the annoying thing that the main URL of my root site http://companyname.sharepoint.com takes people to that blank classic site.
a) I want to hide that root site so nobody finds it via search or 'suggested sites' etc. (I'd also like to hide my content hub publishing site too) Can I do that with permissions? I'm afraid if I remove permissions from that site it will mess up permissions to my other collections since it is the root site.
b) I want to either change the URL of my Hub site from
https://companyname.sharepoint.com/sites/companyname to http://companyname.sharepoint.com? Or perhaps I could somehow redirect that url to my hub site which is our real 'home'?
What do the experts around here think I should I do? Advice gratefully received.
- Hi All,
Did anyone found a solution for changing the SharePoint Online root site collection from the default classic team site to a new modern team site/hub created later ?
Thanks.Unfortunately it is not possible (yet).
If you are part of a very big company, it makes sense that the toplevel is to large to be one comprehensive team. But if your company is like only four people, it doesn't make sense to make seperate teams between those four people.
So Microsoft: take small companies in consideration and allow the whole company to function as one team with one SharePoint site at the top level.
So after a lot of confusion and experimentation, what I ended up doing was enabling this tenant to receive the "targeted release" 365 features. Then I was able try the "new sharepoint admin center preview". From here, I could create a new top level site (not sure if its still a site collection?) (such as domain.sharepoint.com/sites/MyNewSite) - which appears to be the new 365 Groups-based site - though it doesn't show up under the old SharePoint Admin Center as a site collection. And I could use the new modern team site or communication site templates.
But then in the new admin center, there were no controls to turn off external sharing for that site. I then found powershell commands to disable external sharing for one of the sites.
So as far as I can tell, I've now ended up with 2 new top level sites using new modern team site templates and have one with external sharing enabled and one with external sharing disabled. Took a lot of researching and jumping through hoops but I feel like I'm in a good situation to start building out the sites now.
Jason Hartman
- You should not delete the root site collection in your tenant, since you can run into unexpected side effects. Best thing here is to create a new communication site and move contents from the root site to the new communication site created
