On Friday evening, February 5th, a new version of the Minddistrict platform will go into production. In this release note, you'll find all updates. Enjoy the new version of Minddistrict! 

Do you have questions about the Minddistrict platform or app? Visit our online support site



Improvements in conversations

This update is relevant for all users 

In the conversation functionality a number of improvements have been made. This will make the conversations more comprehensive and unread messages can easily be found within long conversations. As of February 5th, the following improvements will be online: 

  • Within a conversation, the label 'unread' is used instead of 'new' when there are unread messages in the conversation. This 'unread' label will disappear once the message once the message has been on the recipients screen.
  • Users will 'land' on the oldest unread message when opening a conversation.
  • If there are more unread messages in the conversation, this is indicated by means of a floating button at the bottom right of the conversation. The user can quickly jump to these messages via this button. Read and unread messages are separated from each other by means of a dividing line 'last'. 
  • Own messages are displayed in a different colour (grey) than the received messages (blue). 
  • The conversation screen is bigger than before.
Are there still old unread messages in long conversations? You will automatically end up there. The counter of unread messages is then automatically being updated because the message is considered read. Fast forward to the next unread message in the same conversation? Click the floating button at the bottom right of the conversation window.

The improvements in the conversations are also being implemented in the new version of the Minddistrict App. This new version will be available about a week after February 5th!

Transfer of ownership in conversations

This update is relevant for professionals 

Old situation

Until now, the professional who started a conversation was automatically the owner. If this owner was not present in a conversation, no one was in control of this conversation. As a result, it was impossible to make any of the following adjustments, because only an owner has the rights to do this:

  • Change the subject of the conversation
  • Add or remove participants in the conversation
  • Invite or remove a guest (if this option is activated on the platform)

New Situation

In the new situation, professionals can transfer or take over the ownership of a conversation via a dropdown menu. This menu is behind the name of the participants. Via the same dropdown menu, the owner can remove participants from the conversation.

Note: It is required that the new owner is related to all participants in the conversation. Is this not the case? Then a warning appears that the professional cannot be the owner. If the professional is related to all participants there will be a confirmation modal showing the option to transfer the ownership.

Minddistrict no longer accessible via Internet Explorer

This update is relevant for all users 

Microsoft has stopped supporting Windows 7 since January 2020. In addition, the company has announced that it advises other companies not to use Internet Explorer anymore. Minddistrict strives for optimal operation and security of the platforms. Therefore soon Minddistrict will no longer be accessible via Internet Explorer.

When a user opens the platform via Internet Explorer, a page appears saying that Internet Explorer is no longer supported. 

This page lists the browsers we recommend to use: Chrome, Firefox, Edge and Safari.

NoteAs of February 5th, the platforms on the following environments will no longer be accessible via Internet Explorer: 

  • content.minddistrict.com 
  • training.minddistrict.com 
  • sandbox.minddistrict.com 

On April 2 also production platforms will no longer be accessible via Internet Explorer! 

Tip: Actively communicate this to users.

Session timeout configurable

This update is relevant for Application managers 

By default, a session was ended after 60 minutes of inactivity. From now on, the application manager can adjust this period in the configuration. The time can be set between 1 and 60 minutes. This can be set separately for professionals and for clients, friends and guests. The default time remains 60 minutes.

This configuration is not available by default. Interested? Please contact the Minddistrict Servicedesk


New module: Worry less

The new module ‘Worry Less’ consists of 5 sessions. It focuses on understanding worry, but also on ways to start worrying less. Exercises that are offered are: using a thought record, having a 'Worry time' and problem solving. This module also includes a session about relapse prevention and explains ‘Hypothetical worries’ and ‘Practical worries’.

More information

Technical update

Extra server: add IP addresses to whitelists

This update is relevant for application managers if using whitelists 

On February 5th Minddistrict will add an extra server. Do you use IP whitelisting / firewalling for our IP addresses? Please add the following IP addresses to your whitelist: and 2001: 4c10: 1001 :: 174

Configuration: notification after change of e-mail address

This update is relevant for application managers 

A new option has been added to the configuration of the e-mail settings. This allows the application manager to (de) activate if users receive an email when their email address has been changed. This option for sending such an e-mail is set to 'on' by default and can be set separately for professionals and for clients. If the option is on, users will receive an email saying that they can log in with this new email address.

Rest-API: New endpoints for conversations added

This update is relevant for organisations usign Rest-API 

A conversations Rest-API endpoint has been added to extract conversations metadata from platforms.
The ‘changes REST API endpoint’ has been extended. So external platforms can efficiently query which users have any changes in their conversations. This makes it possible to only request the metadata for that subset of users.

The technical documentation about the REST API will be updated with this new information