Skip to main content

Hi everybody,

I’m referring to this topic, as I can’t comment there:

First of all: Thanks for implementing this tool, Gainsight!

I have a few questions about it.

  • Will every author receive the DSA Moderation mail, no matter their personal notification preferences?
  • Will a user be able to opt-out of receiving DSA Moderations mails? Or is this considered a “mandatory” mail that you cannot opt-out of?
  • Gainsight provided the {topic_title} token. Is there also a token to directly link to the post? → Background: When a comment is being edited (instead of the topic post), I want to be able to link to the comment that has been edited.

Thanks!

Hi ​@bjoern_schulze!

 

Will every author receive the DSA Moderation mail, no matter their personal notification preferences?

Will a user be able to opt-out of receiving DSA Moderations mails? Or is this considered a “mandatory” mail that you cannot opt-out of?

 

Considering the fact that informing a user of a change to their posts is necessary to comply to EU regulations under the Digital Services Act, we did not include the possibility of a user to unsubscribe from this particular communication as it goes against the logic of it, at least as of now.

Nevertheless, we can dig deeper into it if you have concerns around this particular point - I am more than happy to discuss this further if necessary.

 

Gainsight provided the {topic_title} token. Is there also a token to directly link to the post? → Background: When a comment is being edited (instead of the topic post), I want to be able to link to the comment that has been edited.

 

I am not entirely sure if a token like {post_id} is possible to include here but I will ask the team that takes care of the email notifications setup.

 

If you have any other questions or feedback, feel free to let me know! :)


I have an issue correctly implementing the {moderation_description} into the system email.

Gainsight seems to automatically add HTML to the phrase. It looks like this:

</p><p>{moderation_description}</p> 

This causes the surrounding custom HTML to “break”, as the current paragraph (with its styling) is being closed and a new paragraph (without any custom styling) is being added.

I suggest to remove all HTML from the phrase and to let customers style the {moderation_description} as they need to, in order to fit it into their system email template.

Thank you!


Hi ​@hhugo, thank you for your response!

If notifying the user about edits is mandatory and they aren’t supposed to be able to opt-out, then I’m perfectly fine with not having user settings for that. :)


I have an issue correctly implementing the {moderation_description} into the system email.

Gainsight seems to automatically add HTML to the phrase. It looks like this:

</p><p>{moderation_description}</p> 

This causes the surrounding custom HTML to “break”, as the current paragraph (with its styling) is being closed and a new paragraph (without any custom styling) is being added.

I suggest to remove all HTML from the phrase and to let customers style the {moderation_description} as they need to, in order to fit it into their system email template.

Thank you!

 

@bjoern_schulze I did not fully understand this as you mention “implementing the {moderation_description} into the system email”. But then mention “Gainsight seems to automatically add HTML to the phrase”.

What exactly are you trying to edit? The system email or a custom phrase for one of the DSA descriptions?

I just tested editing the custom phrases on my end and they are working quite alright.

 

Could I kindly ask you to reach out to support with a recording of what is erroring on your end with this so they can assess what is going on? Feel free to mention this topic in the ticket and we can triage from there.


@hhugo Thanks, I’ll create a ticket.

To rephrase the issue (in case anyone else comes across this):

I can create and edit the custom phrases fine, e.g. “dsadescription.privacy_violation”. But when I use the token {moderation_description} in order to include the custom phrase into the system email, some HTML is being added automatically.

Expected HTML (simplified):

<p>
Hello {recipient_username}, we have edited your post in the topic "<a href="{topic_url}">{topic_title}</a>".
<br/><br/>
Reason: {moderation_reason}
<br/><br/>
Details: {moderation_description}
<br/><br/>
Greetings, <br/> Community team
</p>

Actual HTML:

<p>
Hello {recipient_username}, we have edited your post in the topic "<a href="{topic_url}">{topic_title}</a>".
<br/><br/>
Reason: {moderation_reason}
<br/><br/>
Details:
</p><p>{moderation_description}</p>
<br/><br/>
Greetings, <br/> Community team
</p>

This causes the {moderation_description} to break the surrounding HTML. Also, it’s not possible to style the {moderation_description}, therefore it looks out of place in the email.


Thank you Gainsight, for quickly fixing the small HTML issue, it works like a charm now.

 

Gainsight provided the {topic_title} token. Is there also a token to directly link to the post? → Background: When a comment is being edited (instead of the topic post), I want to be able to link to the comment that has been edited.

I am not entirely sure if a token like {post_id} is possible to include here but I will ask the team that takes care of the email notifications setup.

Can you give me an update here? My legal team strongly advised me to be able to link to the actual piece of content that has been edited, instead of just linking to the topic.

In a community where topics can have pages and pages of comments (including multiple comments by the same user), not being able to give the user a link to the actual comment the notification is referring to, can (and will) lead to misunderstandings.


Hi ​@bjoern_schulze sorry for the delay in replying here.

 

I discussed this with the team that owns System Emails and they already have a ticket in their queue to allow adding the post URL to this particular message.


Hey ​@bjoern_schulze!

 

The team that manages email notifications implemented the variables for the DSA system email.

You will now find {post_url} which will contain the topic URL if the topic (opening post) is updated or the reply URL if a reply is updated.

Apart from this, the old topic_url can be updated to post_url, but it has backward compatibility.

 

Feel free to test and give us some feedback if something is not working as expected.