Forum Discussion
Struggling with Team naming and organization
I really wish teams gave us little more flexibility to Team names and their underlying alias and SharePoint url name.
We basically create teams based upon work getting done. more project or program based. some functional groups like departments but we are so small a department is likely to be a single person.
it would be nice if you can rename a team a team and the SharePoint url. For example we have a program it has a team. But we are adding a second location of that program. It would be good to rename the existing team with some sort of location info including the url so that the urls are confusing either. Because we are also planning a communication site which would make sense to have the old url.
I may be just overthinking things and it is simply not really necessary in this worlds for the SharePoint url's to be understandable and hackable (like you can guess what the url should be). But it seems like you would want it for the alias assigned to the underlying office 365 group.
Another reason to want more control over the url is you may want to the name of the group to be one thing. But that name might be on the longer side and you just want to abbreviate the url.
- I've just learned to stop overthinking the URL's and go off the Display names of the groups / attached sites. I mean you could always go with a generic name, then rename it after creation I suppose.
When it comes to naming conventions in general for me it's always
Comm sites or sharepoint only sites are just the name, such as (Technology) for our Org facing site. Our private Team attached site is always Technology Team etc. Projects follow same structure, if it has a Team it's MOC Team, or Invoice Tracking Project Team etc. I try not to overthink it and keep it pretty much to if it has a Team tied to it we tack Team to the end etc.
6 Replies
- This is great feedback, but the best place to put it is microsoftTeams.uservoice.com as the Product group uses this to collect and go through feedback and see what has the highest need. I suggest go putting this feedback there! Search if someone else may have put the same idea out and add your comments to it, or create a new one. You can always post back up here for votes!
ChrisWebbTech Thanks, when I set out I thought I was going to be more asking people how they handle organization/renaming as they grow and new teams get created and original organization/naming doesn't seem to fit any longer.
I can certainly post this as a feature, and I will. But kind of wondering what people are doing, maybe there is a best practice someone could share, that would keep me from creating the problems I am having.
- I've just learned to stop overthinking the URL's and go off the Display names of the groups / attached sites. I mean you could always go with a generic name, then rename it after creation I suppose.
When it comes to naming conventions in general for me it's always
Comm sites or sharepoint only sites are just the name, such as (Technology) for our Org facing site. Our private Team attached site is always Technology Team etc. Projects follow same structure, if it has a Team it's MOC Team, or Invoice Tracking Project Team etc. I try not to overthink it and keep it pretty much to if it has a Team tied to it we tack Team to the end etc.
