Your comments

In order to separate team communication from client communication, imagine the following:


1. There would be a separate role called 'client'


2. The chat could be separated into: team chat and client chat (2 separated chat channels, accessing the client-chat should be an optional property of a team member)


3. The topics could be separated into: team topics and client topics (2 separated topic channels, accessing the client-topics should be an optional property of a team member)


4. The tasks should be visible to the client, limited by the following fields (title (read-only), or if available the title is overridden by a specific client-title (read-only) description (read-only), or if available the description is overridden by a specific client-description (read-only), assignees (read-only), attachments (read-only but possible to add new) client-comments (editable)


5. That it would be possible to have an optional property for a category on the task board which says: client can add tasks (title, client-description, attachments, client-comments). In this case no email is needed anymore and the client is able to add tasks to the board containing the initial info. The admin is responsible for the follow up on the task board.


With a feature like this Ryver is not only about team communication, but also about client communication. It becomes -the hub- between the team on the one side and the client on the other side. As an admin you are able to manage who can communicate with the client and who can't. Internally everyone can talk freely since the internal communication stays separate from the client communication. In case you work with co-workers abroad, using another language then the client does, languages stay separated.