Team Levels

I'm not sure what to call this so for now I've called it Team Levels but essentially what I was wondering about was permissions within your company members.

I've seen a few comments regarding contractors and team, and private messages etc. and I wondered if there was a way to add functionality for a member of your team to not see the private messages. I.e. create members of a company team but designate which ones are allowed to see private messages.

Another version of this idea might be two levels of team private messages --- almost like channels. Channel 1, is for leaders/manager, channel 2 for all members or something like that (and others can use this as fits their organization for example . internal staff channel 1, remote team channel 2.

Another idea along these lines would be "contract" team, where you can have companies and team members who can participate in the project but not be seen by "client" companies. (someone commented on this for transparency sake you should be letting your client know contractors are involved, I'm not here to debate that... but either way having contractor conversations and work posted will be confusing for the client so I would say it should be optional to not have these appear, both company and their contributions in whatever form, milestones etc.)

I don't know how hard these ideas would be to implement, but wanted to suggest them as ideas to solve the privacy and confusion issues that come with teams in projects.

I'd also like to be able to toggle my view between hiding private messages, and showing private messages --- there may be a time when you are looking at the page with your client, and do not want the "entries" for the private messages showing. Also sometimes you just want to be comfortable that the message have been correctly marked as hidden... this would be a quick way to be sure they aren't showing.

I know this message presents a tall order -- I'm just brainstorming here, hoping the best ideas will be supported by others and implemented should they provide a benefit. I'm all for the "less is more" approach... so less useless features, and more of the best ideas implemented.

There have been some great ones on these forums.