# Login required to see topic info

**URL:** https://meta.discourse.org/t/login-required-to-see-topic-info/78512
**Category:** Support
**Created:** [January 19, 2018, 11:33pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512 "2018-01-19T23:33:03Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 19, 2018, 11:33pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/1 "2018-01-19T23:33:03Z")

</div>

Is there a way to make the topic list visible of a given category, but remove the ability to see the content of the topic without logging in?

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [January 19, 2018, 11:45pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/2 "2018-01-19T23:45:54Z")

</div>

Not with Discourse by itself, but you may be interested in this plugin. Make sure you don’t use it for any sensitive information - the topic contents is still visible in search results

> [@Discourse Category Lockdown](https://meta.discourse.org/t/advertise-activity-in-a-private-category-discourse-category-lockdown/70649):
>
> This plugin allows you to restrict access to topic pages in a category. Topic titles will still show up in topic lists, search, user activity & digest emails. This is a great way to advertise the activity in a “members-only” category, which may charge for access. It IS NOT designed to keep the contents of the category 100% private - if someone is determined enough they will be able to piece together the content from search results. Each category has a couple of new settings in the Security tab…

---

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 20, 2018, 12:13am UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/3 "2018-01-20T00:13:19Z")

</div>

Thanks for the link.

May I ask if one is able to “hide” the contents of say… a link, unless a member is logged in?

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [January 20, 2018, 12:29am UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/4 "2018-01-20T00:29:15Z")

</div>

I haven’t used it before, but maybe this plugin could help:

[https://meta.discourse.org/t/content-lock-bbcode/48293?u=david\_taylor](https://meta.discourse.org/t/content-lock-bbcode/48293)

---

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 20, 2018, 12:40am UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/5 "2018-01-20T00:40:32Z")

</div>

Thank you. Seems everything is a plugin, odd such things aren’t supported on install.

I appreciate you taking the time to help.

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [January 20, 2018, 12:44am UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/6 "2018-01-20T00:44:41Z")

</div>

> [@tetra](#):
>
> odd such things aren’t supported on install

That’s because it’s an extremely niche feature; check how many (or rather, how few) previous topics there are about this feature, and you’ll notice that the vast majority of Discourse sites don’t need this – so, it doesn’t go in core.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 20, 2018, 4:37am UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/7 "2018-01-20T04:37:06Z")

</div>

What is your problem with a plugin for such a feature?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [January 20, 2018, 6:42am UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/8 "2018-01-20T06:42:37Z")

</div>

Oddly enough, this request comes up a fair bit. But I believe it is for ultimately negative reasons — people want to play the peek-a-boo content game, show people topic titles then demand they create an account if they wish to see more.

---

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [January 20, 2018, 6:52am UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/9 "2018-01-20T06:52:15Z")

</div>

> [@codinghorror](#):
>
> this request comes up a fair bit

TBH, I’m surprised that it does. Considering the fact that Google and other search engines are “non-logged in users” I would think that most would not want to trade off losing content visibility in exchange for teasing visitors into registering based solely on what topic titles they can see. If they ever find their way to the forum to begin with.

---

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 20, 2018, 11:53am UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/10 "2018-01-20T11:53:52Z")

</div>

I never even thought of that. Lol Doesn’t really make sense though as you’re going to lose a ton of members that way.

---

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 20, 2018, 11:59am UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/11 "2018-01-20T11:59:55Z")

</div>

For me, regardless, I’m going to have a private category. Making it completely invisible to the rest of the community doesn’t really make sense to me… No one would even know it exists.

---

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 20, 2018, 12:05pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/12 "2018-01-20T12:05:18Z")

</div>

I don’t like messing with things. Even small things. I want to install, and go… default theme, default software, default everything.

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [January 20, 2018, 10:28pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/13 "2018-01-20T22:28:51Z")

</div>

> [@tetra](#):
>
> I want to install, and go… default theme, default software, default everything.

Then you get default behaviour, which is to not bait-and-switch search engine users.

---

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 20, 2018, 10:57pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/15 "2018-01-20T22:57:17Z")

</div>

> [@mpalmer](#):
>
> Then you get default behaviour, which is to not bait-and-switch search engine users.

You realize just because someone “can” do something with a feature, doesn’t necessarily mean they “will” do something with a feature. :S

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [January 20, 2018, 11:07pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/16 "2018-01-20T23:07:48Z")

</div>

> [@tetra](#):
>
> You realize just because someone “can” do something with a feature, doesn’t necessarily mean they “will” do something with a feature. :S

Yes, and I’m sure you realize that even if you’re not interpreting your own intentions that way, the act of showing topic titles without allowing access to posts **is** considered to be bait-and-switch. The expected behavior by users is that **if they can see the topics, they should be able to read them**. Deviating from that user experience is widely accepted to be a dick-move, which is why Discourse doesn’t have such functionality baked-in.

The team aren’t inflexible, if someone presents a well thought-out case for a feature or change they’ll be willing to accept a PR or even build it themselves. The whole point is that nobody has been able to make a case that doesn’t fall into the above category.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [January 20, 2018, 11:09pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/17 "2018-01-20T23:09:09Z")

</div>

Can you link to live examples of sites on the web that do what you want? So we can better understand what you are trying to accomplish?

---

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 20, 2018, 11:14pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/18 "2018-01-20T23:14:48Z")

</div>

> [@steve\_pd](#):
>
> Yes, and I’m sure you realize that even if you’re not interpreting your own intentions that way, the act of showing topic titles without allowing access to posts is considered to be bait-and-switch.

… can you please explain how as long as the titles of threads contain the content suggested, it’s meeting the criteria of “bait-and-switch”??

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [January 20, 2018, 11:18pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/19 "2018-01-20T23:18:23Z")

</div>

> [@tetra](#):
>
> … can you please explain how as long as the titles of threads contain the content suggested, it’s meeting the criteria of “bait-and-switch”??

> [@steve\_pd](#):
>
> The expected behavior by users is that if they can see the topics, they should be able to read them.

^ The above covers it succinctly enough, if users are presented with a resource they should be able to access it. The act of forcing users to register just to be able to read is user-hostile. Many of us will find an alternative site if presented by a login prompt. **Your role when running a community is to give them positive reasons to register, because they want to belong to the community and participate**.

---

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 20, 2018, 11:22pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/20 "2018-01-20T23:22:41Z")

</div>

> [@codinghorror](#):
>
> Can you link to live examples of sites on the web that do what you want? So we can better understand what you are trying to accomplish?

I can give an example easily. I was a member at [slingshotforum.com](http://slingshotforum.com), they have a section for supporting members. Topic titles are seen, content is not. The idea is that if you want to join in the dialogue on those topics, you have to become a premium member.

 ![image](https://global.discourse-cdn.com/meta/original/3X/f/2/f20850106c819c52556b446152432a92b0428e0a.jpg)

I can’t find the logic in having permissions to prevent anyone from even knowing a category exists? Which is how it’s currently set up, unless I’m mistaken? (which I could be).

---

<div class="post-metadata">

### Author: ![tetra](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tetra](https://meta.discourse.org/u/tetra)
#### Post date: [January 20, 2018, 11:27pm UTC](https://meta.discourse.org/t/login-required-to-see-topic-info/78512/21 "2018-01-20T23:27:22Z")

</div>

> [@steve\_pd](#):
>
> ^ The above covers it succinctly enough, if users are presented with a resource they should be able to access it. The act of forcing users to register just to be able to read is user-hostile. Many of us will find an alternative site if presented by a login prompt. Your role when running a community is to give them positive reasons to register, because they want to belong to the community and participate.

No, it really doesn’t… I mean, it’s fine if you want to say you don’t like the idea, no problem. However, it really doesn’t meet the criteria of “bait-and-switch”. No doubt however, someone could use the feature in that manner.

You seem to have a very broad view of what is “user-hostile”. If I want to read someones Facebook page, and the comments on posts, I need to be registered. Is this also user-hostile to you? Personally I see no issue with this.

[Next page](https://meta.discourse.org/t/login-required-to-see-topic-info/78512.md?page=2)
