Ability to specify user groups that are independent from Workspace limitations for the purpose of group @mentions.
In our company, we use several workspaces, but there are two primary workspaces: we've named them 'Customer Care' and 'Guest Support'. For various reasons, the majority of our users need to be members of both workspaces.
In order to quickly inform a large group of users, our support staff are using '@Guest Support' mentions. Unfortunately, the information being posted is generally only relevant to the support staff, and our staff that spend most of their time in Customer Care (but still need access to Guest Support) are constantly being spammed with useless notifications. If there was an option to define user groups on an organizational level (in the 'User Management' module), the @mention tool would become much more powerful.
Thanks for the followup with the details about trying that. We'll save this input so hopefully in the future something can be done to provide this functionality. :)
/Joseph – PodioComment actions
Thank you for the details on your use case and this feedback. One possible solution in the meantime is to make a new workspace for support staff. Even if that workspace is not used explicitly for any business functions, it would serve as a way to @mention that group that should see those data.
Would that work? I'll save this input for consideration by our product team going forward as well. Thanks again! :)
/Joseph – Podio
FYI, we've experimented with your suggestion and it's a partial solution, but not complete. Unfortunately, people who are not part of the 'phantom' workspace can't use the @mention to that workspace. It works internally for the people within their own 'department', but not from one department to another.
The need for user groups still exists. This would allow individuals to quickly tag specific groups of users.
I have the same need as expressed by Garrett. In 3 years time, did you work something up ?
I have used the search engine and I only come up with the same option as you offered, i.e. using workspaces. However, it has the drawback mentioned by Garrett and it is quite annoying.
Thank you !
Please sign in to leave a comment.