Manage Direct Messaging Permissions

You may wish to prevent some users from being able to open a direct message(DM) chat with other users of certain roles. This article will help you to add these restrictions.

You will need the Manage organisation member roles permission to be able to add these restrictions. If you do not have the permissions, you will need ask the organisation owner or users with this permission to make these changes.


In order to manage roles, you need to access the organisation settings page.

Enter the Organisation Settings

To begin, you need to be in the Organisation Screen. If you are not, refer to this article to exit a room. The associated controls are at the top left of the screen.



Ensure that you are in the correct organisation.


Click the Settings button next to the organisation name on the left panel

Select Roles.

Select the role that you want to restrict DM permissions for.

Click the box under Starts direct message with to add roles that DM chats can be opened with. In this case, it means that the user with Student role are allowed to open DM chats with users of Tutor / Teacher role.

This does not necessarily apply the other way round, so users with Tutor / Teacher role do not necessarily have the permission to open DM chats with users of Student role. You can amend the permission for different roles so that roles have different restriction of who they can send DMs to.

Click the cross to remove the roles that DM chats can be opened with. In this case, deleting Student means that users with the Student role are no longer allowed to open DM chats with other users of Student role.

Note that however, if a user of this role(Student) already opened a DM chat with a user of the restricted role(Student) before, they can continue to send messages to that specific user. If Student A has already sent a DM to Student B before, they will continue to be able to send messages to Student B even though they cannot open DM chats with other Students.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us