# Prevent Slack from unfurling anything for login-required sites

**URL:** <https://meta.discourse.org/t/prevent-slack-from-unfurling-anything-for-login-required-sites/75233>\
**Category:** Product Support\
**Created:** [Décembre 2, 2017, 12:52 UTC](https://meta.discourse.org/t/prevent-slack-from-unfurling-anything-for-login-required-sites/75233 "2017-12-02T12:52:40Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)\
**Post date:** [Décembre 2, 2017, 12:52 UTC](https://meta.discourse.org/t/prevent-slack-from-unfurling-anything-for-login-required-sites/75233/1 "2017-12-02T12:52:40Z")

</div>

Our Discourse instance is private and we use the [discourse-slackdoor](https://meta.discourse.org/t/discourse-slackdoor-plugin/44632) plugin to allow Slack to unfurl the contents of posts that are shared in our private Slack.

But Slack still tries to do it’s _own_ unfurling of the links, which is kind of annoying because all it is able to get is the site title and description.

So every link shared in Slack ends up getting the same, additional attachment from Slack that looks kinda like this:

 ![repetitive-unfurl](https://global.discourse-cdn.com/meta/original/3X/7/5/75daf77468ea4e61dc98e2b9605dd257fc054e8f.png)

I end up clicking the ‘x’ on that attachment every time…

Is there something simple we can do to prevent this attachment from getting added in the first place?

Should login-required sites just get the metadata that Slack requires to generate that attachment redacted by default?

---

_[View the full topic](https://meta.discourse.org/t/prevent-slack-from-unfurling-anything-for-login-required-sites/75233)._