Allow users to be 'primary team member' of more than one team
Currently, a user can be a 'primary' member of only one team. The user can be added to other teams as an 'additional team member', but many team features are unavailable to these 'additional' users (see list of restrictions below).
This is problematic and causing us considerable pain because some users need full access to multiple teams, e.g. an individual who is multi-role, or management/supervisory staff who need to monitor what goes on in the team. This is particularly true in smaller businesses. The one primary team restriction seems unjustifiable .
These users will not be included in any team reports, routing rules (e.g., conversation routing rules), team notifications (e.g., form submission email notifications to a team), or workflow rotation actions. They will also not be able to view any custom records views set up for the team.
The solution is to allow users to be primary members of multiple teams.
We have a client with users that exist in multiple teams.
We need users to be in multiple teams (or additional team members), so that we can use those teams in workflows to send internal emails / notifications.
Chipping in with my +1 too. This seems like a completely needless restriction on capabilites. Like many others, I have users straddling Teams and having to micro-manage individual memberships for notifications rather than simply notify a team is a pest
Needs to be fixed. Almost 3 years ago now the post was made.
Defeats the purpose of having teams that you can use in Workflows.
Instead of "Hardcode" communications to specific users you should be able to use "Teams" to add and remove users. It's nearly impossible if you have multiple Workflows that are hardcoded to users to keep track of who gets what. Much easier to use the "Team" in the Workflow and remove and add new users from it.
