# Link preview werkt niet na het verwijderen van "iedereen" uit de beveiligingsgroep van de categorie
**URL:** https://meta.discourse.org/t/link-preview-not-working-after-removing-everyone-from-categorys-security-group/193478
**Category:** Support
**Created:** [11 juni 2021 om 03:48 UTC](https://meta.discourse.org/t/link-preview-not-working-after-removing-everyone-from-categorys-security-group/193478 "2021-06-11T03:48:53Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@harrylee](https://meta.discourse.org/u/harrylee)
#### Post date: [11 juni 2021 om 03:48 UTC](https://meta.discourse.org/t/link-preview-not-working-after-removing-everyone-from-categorys-security-group/193478/1 "2021-06-11T03:48:53Z")
Hello,
It’s my first post and I am sorry that it’s not something that helps others rather asking for help. 😓
We have been using our installation of Discourse on our local server for internal communications for two years. And we like it a lot.
I find Discourse’s topic link preview(Onebox?) one of the best features of Discourse and it has been working great until I change all the categories permission to the same private(closed) group only removing “everyone”. 😓
I had to do it because we’d like to invite guests to a specific category and we did not want them to see all our internal channels.
I understand that I will not be able to see the topic preview if the security group is different.
But all our category has the same security group called “our company name”.
But still, any topic link except the ones that belong to the same category is not working. 😓
Will that be any way that we can have the topic preview feature with the category not open to “everyone”?
I think I extensively searched the forum but I could not find the topic with the same issue. 🤔
> [@Self Link previews not working for private site](https://meta.discourse.org/t/self-link-previews-not-working-for-private-site/59309/7):
>
> I just tested this locally and oneboxing a login required forum does work. One caveat though: you cannot onebox topics in categories that are not public, because you could expose information to people who can’t see that stuff.
I saw the post above but the problem is that my category A and category B has the same security group. but it’s not just public.
By the way, I think Discourse is the best solution available not only for the public forum but also for internal communication. In my opinion/use case, it’s better than Slack or Teams. We had used both solutions for years especially Slack since it was beta, We switched to Teams from Slack for a while and have been using Discourse for 2 years now.
Thank you for developing and open-sourcing this great solution.
---
### Author:  [@Tris20](https://meta.discourse.org/u/Tris20)
#### Post date: [5 oktober 2021 om 11:52 UTC](https://meta.discourse.org/t/link-preview-not-working-after-removing-everyone-from-categorys-security-group/193478/2 "2021-10-05T11:52:18Z")
I’m also having this same issue. I wanted to onebox something in the subcategory which has the same permissions as the category, but could not do this. The subcategory cannot be public, but it is visable to everyone in the category, so should be suitable for oneboxing
---
### Author:  [@JQ331](https://meta.discourse.org/u/JQ331)
#### Post date: [16 maart 2022 om 17:56 UTC](https://meta.discourse.org/t/link-preview-not-working-after-removing-everyone-from-categorys-security-group/193478/3 "2022-03-16T17:56:20Z")
Having the same issue. Any solution?
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [16 maart 2022 om 18:14 UTC](https://meta.discourse.org/t/link-preview-not-working-after-removing-everyone-from-categorys-security-group/193478/4 "2022-03-16T18:14:23Z")
I quote the bit I want to use, and that works out pretty good. You can even do a small excerpt and use the expand to show the full post. ( **Added after:** if the user has permission to view the category where the quote is from)
> [@On another topic](https://meta.discourse.org/t/217688/5):
>
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus sed malesuada nunc. Cras eu tellus a arcu laoreet congue sed at sem. Morbi quis iaculis dui, at fermentum purus. Curabitur diam neque, imperdiet vitae varius ac, eleifend a sapien. Etiam congue egestas mauris ac varius. Proin eu ligula eu eros sagittis fringilla. Nullam venenatis nunc in est pretium efficitur. Quisque facilisis massa in tellus rhoncus vestibulum.
It says ‘On another topic’ rather than the topic title, so not super smooth, but has been a good workaround for us. 👍 The bonus is that it also keeps its formatting too.
---
### Author:  [@Tris20](https://meta.discourse.org/u/Tris20)
#### Post date: [16 maart 2022 om 21:06 UTC](https://meta.discourse.org/t/link-preview-not-working-after-removing-everyone-from-categorys-security-group/193478/5 "2022-03-16T21:06:59Z")
It also shows a preview even though the topic is private 😲
Interestingly enough the main issue doesn’t occur for me anymore. If a user has access to the category, then they can see the preview.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [16 maart 2022 om 21:41 UTC](https://meta.discourse.org/t/link-preview-not-working-after-removing-everyone-from-categorys-security-group/193478/6 "2022-03-16T21:41:08Z")
You can tweak it a bit so it doesn’t give the expand by adding `full:true` to the quote, or just strip back to the username if you don’t want the ‘On another topic’ link:
> [@On another topic](https://meta.discourse.org/t/217688/5):
>
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus sed malesuada nunc. Cras eu tellus a arcu laoreet congue sed at sem.
> [@JammyDodger](#):
>
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus sed malesuada nunc. Cras eu tellus a arcu laoreet congue sed at sem.
And a bonus third option, getting increasingly low-tech, to just replace the username with the topic title:
> [@FAQs](#):
>
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus sed malesuada nunc. Cras eu tellus a arcu laoreet congue sed at sem.
Though the astonished emoji is making me think I’ve misjudged this in some way. 🙂