That’s exactly what I would advise too. Too many teams become unmanageable and hard to find information. The way I structured our company m is the same with having a projects team but for clients, I have technical team and each channel is the client. In it holds technical info about the client. There are few other channels such as training, tech news, non-work related, etc…Then the sales department would have a Sales team and each channel with the same client but it would hold sales information about the client. We had to separate because we didn’t want the technical team to see information about client’s budgets. But if that’s not requirement, then you could simply have a team called clients and each channel represents a client and in it holds tech, sales, accounts info.
Have you found that having one team for your back office creates functionality issues? If you create a private channel for the executives, it will limit he functionality in their channel because the permissions feed down from the team. For example, you wouldn’t be able to create a plan and planner for the executives that only they could see within that channel.
Thanks for sharing your experience with thai. Is this also true for "shared" channels? I have to test this out again, but I thought I was using a planner for the private channels before. Technically this should work, as both private channels and shared channels create their own site collections and I assumed these came with their own m365 group (which is what planner uses for security)
That's a really good question, for that scenario I would do a folder structure per client. We're sub folders would be for each project for that client.
@@DeShonClark Thank you for your answer, I was struggling with this. In that case I'll be creating channels for the important clients (around 30/40) and for those that need a lot less intern collaboration I'll make 1 'all/misc clients' channel. If I still have issues with the setup I'll schedule a calendly meeting. Thank you!
Welcome Back...we missed you. Sharepoint Friend from Las Palmas Spain 🎉
Thank you! Glad to be back
That’s exactly what I would advise too. Too many teams become unmanageable and hard to find information. The way I structured our company m is the same with having a projects team but for clients, I have technical team and each channel is the client. In it holds technical info about the client. There are few other channels such as training, tech news, non-work related, etc…Then the sales department would have a Sales team and each channel with the same client but it would hold sales information about the client. We had to separate because we didn’t want the technical team to see information about client’s budgets. But if that’s not requirement, then you could simply have a team called clients and each channel represents a client and in it holds tech, sales, accounts info.
I love your approach...super smart
Have you found that having one team for your back office creates functionality issues? If you create a private channel for the executives, it will limit he functionality in their channel because the permissions feed down from the team. For example, you wouldn’t be able to create a plan and planner for the executives that only they could see within that channel.
Thanks for sharing your experience with thai. Is this also true for "shared" channels? I have to test this out again, but I thought I was using a planner for the private channels before. Technically this should work, as both private channels and shared channels create their own site collections and I assumed these came with their own m365 group (which is what planner uses for security)
How would you structure it if there are around 200 clients? For instance for a digital agency.
That's a really good question, for that scenario I would do a folder structure per client. We're sub folders would be for each project for that client.
@@DeShonClark Thank you for your answer, I was struggling with this. In that case I'll be creating channels for the important clients (around 30/40) and for those that need a lot less intern collaboration I'll make 1 'all/misc clients' channel.
If I still have issues with the setup I'll schedule a calendly meeting.
Thank you!
Wait! What! More teams than employees
lol...it's amazing. super confusing...multiple places to store same type of file