#dominoforever | Product Ideas Portal

Please implement this. Its really, really important! Without this function we cannot use Sametime. #GDPR #DSGVO #right of erasure

Would be really nice if this feature would be implemented.
It's possible with the competition, our managers are already thinking about changing.

are there any news? please implement this. its very important.

#GDPR #DSGVO

12 months later .. are there any news ?

I have the feeling that the requirement is not taken seriously enough.

9 months later .. are there any news ?

reducing the chatlogging lifetime makes no sense at all.

This is totally contrary to the concept of Persistent Chats and doesn't solve the problem.

4 months later .. are there any news ?

This is on our roadmap after the November release. There are a lot of implications and policies to consider when we provide this e.g. it'll have to be a setting that can be controlled at org level by the admin due to archival needs by certain orgs. We are looking into how best to provide this option to end users considering all scenarios e.g. does the chat get deleted from the sender and all receivers client? Does it also get deleted from server side or does it get archived and flagged on server so it doesn't show up in user's clients? All this is being considered for the release after November one.

Are there sny news? We urgently need this. Otherwise we cannot upgrade our users to Sametime 11.

Our Sametime Server 11.0FP1 is StandBy since April,

the updates Sametime 11.0FP2 is StandBy since August

But we cannot switch our users to the new server if the users cannot delete its own chat history.

I have worked with another customer today also interested in this enhancement.

Best Regards, Keith Kopanski

Senior Product Support Engineer, HCL Sametime

Are there any news? When can we expect the implementation? Our Sametime Server 11.0FP1 is StandBy since April, but we cannot switch our users to the new server if the users cannot delete its own chat history.

For us having the possibilities for the user to delete themself parts and full chat history is an absolute must. Without that user delete function we will not be able to use Sametime anymore.

Passwords do not belong in a chat - everyone should know that. But there are certainly other examples where trustworthy content may be transmitted, but the sender did not see it that way.

@Thomas

BTW: default for chatlogging lifetime is 90d / see administration guide or chatlogging.ini

CL_MONGO_HISTORY_TTL=90

The thing is: Even if it is GDPR- compliant: Some times I chat with colleagues and they e.g chat me a password for me to test something... and this password now sits there... in their and in my chat... visible for every bypasser without any possibility to be removed before the 30day or even 7day limit...

Nevertheless, the user should always have the possibility to delete it himself. Status changed to Likely to implement. That gives us hope. Thank you.

Default lifetime of the chat history is 30 days. Administrators can reduce this time to (e.g.) 7 days. While the response time for a GDPR deletion request is 30 days. So even the default setting would be supporting the timeline requested by GDPR.

Is there a plan when it will be possible that a user can delete its specific persistent chat on its own? We want to rollout Sametime 11, but if the user cannot delete it, the the user will not accept Sametime. This is very urgent !

Please implement this as soon as possible. The users expect this. If a user couldn't delete its chat history this will result in non-acceptance and consequently in not using Sametime

Please implement this as soon as possible. The users expect this. If a user couldn't delete its chat history this will result in non-acceptance and consequently in not using Sametime. #GDPR #DSGVO