Best practice for using internal department teams and company-wide projects?

%3CLINGO-SUB%20id%3D%22lingo-sub-1675463%22%20slang%3D%22en-US%22%3EBest%20practice%20for%20using%20internal%20department%20teams%20and%20company-wide%20projects%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1675463%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20created%2C%20among%20others%2C%20the%20following%20internal%20department%20teams%20in%20our%20Teams%20app%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EAll%3C%2FLI%3E%3CLI%3EAccounting%3C%2FLI%3E%3CLI%3EClient%20Services%3C%2FLI%3E%3CLI%3EMarketing%3C%2FLI%3E%3CLI%3ESales%3C%2FLI%3E%3CLI%3ETech%3C%2FLI%3E%3C%2FUL%3E%3CP%3EEach%20team%20has%20their%20own%20channels%20for%20projects%20for%20which%20their%20department%20is%20the%20primary%20champion.%20For%20example%2C%20most%20client%20projects%20are%20set%20up%20as%20channels%20within%20'Client%20Services'%20team%2C%20but%20the%20entire%20company%20should%20have%20access%20to%20those.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20problem%20we%20have%20is%20that%20most%20projects%20(channels)%20need%20to%20be%20accessible%20by%20everyone.%20To%20get%20around%20this%2C%20my%20boss%20added%20all%20staff%20members%20as%20a%20member%20to%20every%20team.%20One%20of%20the%20problems%20that%20creates%20is%20any%26nbsp%3B%40%20mention%20of%20a%20team%20is%20going%20to%20all%20staff%2C%20because%20all%20staff%20are%20members%20of%20everything.%20%40%20Tech%20is%20the%20entire%20company%2C%20and%20%40%20Accounting%20is%20the%20entire%20company%2C%20which%20makes%20those%20useless.%20Ideally%20we%20would%20have%20%22members%22%20of%20a%20Team%2C%20and%20then%20%3CEM%3Einternal%3C%2FEM%3E%26nbsp%3Bguests%20of%20that%20Team%20who%20are%20able%20to%20browse%20and%20access%20its%20resources%2C%20but%20it%20appears%20guests%20are%20only%20for%20external%20users%2C%20and%20it%20doesn't%20work%20like%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20better%20approach%20to%20set%20up%20our%20teams%2Fchannels%20so%20that%20we%20can%20have%20company-wide%20access%20to%20most%20projects%20but%20also%20leverage%20internal%20department%20teams%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1675463%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EBest%20Practices%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETips%20%26amp%3B%20Tricks%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1676908%22%20slang%3D%22en-US%22%3ERe%3A%20Best%20practice%20for%20using%20internal%20department%20teams%20and%20company-wide%20projects%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1676908%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F796296%22%20target%3D%22_blank%22%3E%40michaelsoutherton%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20access%20to%20Teams%2FChannels%20then%20you%20have%20to%20add%20everyone%20into%20the%20Team%20to%20get%20access%20to%20the%20channels.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20thing%20you%20could%20look%20at%20is%20do%20your%20users%20just%20need%20access%20to%20the%20files%20in%20the%20Teams%20and%20then%20give%20them%20access%20to%20the%20SharePoint%20document%20libraries.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

We have created, among others, the following internal department teams in our Teams app:

 

  • All
  • Accounting
  • Client Services
  • Marketing
  • Sales
  • Tech

Each team has their own channels for projects for which their department is the primary champion. For example, most client projects are set up as channels within 'Client Services' team, but the entire company should have access to those.

 

The problem we have is that most projects (channels) need to be accessible by everyone. To get around this, my boss added all staff members as a member to every team. One of the problems that creates is any @ mention of a team is going to all staff, because all staff are members of everything. @ Tech is the entire company, and @ Accounting is the entire company, which makes those useless. Ideally we would have "members" of a Team, and then internal guests of that Team who are able to browse and access its resources, but it appears guests are only for external users, and it doesn't work like that.

 

Is there a better approach to set up our teams/channels so that we can have company-wide access to most projects but also leverage internal department teams?

1 Reply
Highlighted

@michaelsoutherton 

 

For access to Teams/Channels then you have to add everyone into the Team to get access to the channels. 

 

One thing you could look at is do your users just need access to the files in the Teams and then give them access to the SharePoint document libraries.