# Force signin plugin

**URL:** https://meta.discourse.org/t/force-signin-plugin/60271
**Category:** Plugin
**Created:** [April 1, 2017, 5:04am UTC](https://meta.discourse.org/t/force-signin-plugin/60271 "2017-04-01T05:04:14Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![net\_deamon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/net_deamon/32/70126_2.png) [@net\_deamon](https://meta.discourse.org/u/net_deamon)
#### Post date: [April 1, 2017, 5:04am UTC](https://meta.discourse.org/t/force-signin-plugin/60271/1 "2017-04-01T05:04:14Z")

</div>

**Why this plugin?**

The default option in discourse to force signin users is to completely hide the content behind, and show text to signin users.

If you want something like Quora, where users will be shown login modal, you can use force-signin plugin.  
This plugin will show signin modal if the user is not signed in.

**Options available are**

- Force signin in home page
- Force signin in topics page
- Allow user to close signin modal

U can download the plugin from here  
[https://github.com/netdeamon/force-signin](https://github.com/netdeamon/force-signin)

**Screenshot**

 ![](https://global.discourse-cdn.com/meta/original/3X/5/5/55180e7d5777a4cc59ab3f1f35aca2859362a38f.png)

I will be adding more features to this plugin. Some things that are in my mind are

- Allow customizing text in login modal

Suggestions and comments are welcome !!

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [April 1, 2017, 1:47pm UTC](https://meta.discourse.org/t/force-signin-plugin/60271/2 "2017-04-01T13:47:16Z")

</div>

How does this compare to?

> [@Guest Gate (Sign Up Popup Plugin)](https://meta.discourse.org/t/guest-gate-sign-up-popup-plugin/56625):
>
> In April 2022, the Guest Gate plugin was converted into a theme component by @Don. This plugin is now #deprecated. This is a more permanent post for a plugin that @vinothkannans created and I forked recently. Many thanks to @vinothkannans for doing the hard work of wiring up the main logic, @ljpp for stirring the original conversation, and @DiscourseMetrics.com for providing the impetus behind a customized modal. You have two main gate options: Generic gate Custom gate And tertiary opti…

---

<div class="post-metadata">

### Author: ![net\_deamon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/net_deamon/32/70126_2.png) [@net\_deamon](https://meta.discourse.org/u/net_deamon)
#### Post date: [April 1, 2017, 4:37pm UTC](https://meta.discourse.org/t/force-signin-plugin/60271/3 "2017-04-01T16:37:45Z")

</div>

I totally missed this plugin…  
Thanks for the link.

I installed the plugin in my local machine. Some of the differences I could find was

1. **force-signin** allows to force signin selectively on home page and/or topics page. This I could not find in guest-gate plugin

2. In the guest-gate, the “x button disabled” setting only disables the close button in first popup. The user can still close the “Log in” popup and bypass the signin. Compared to this, in the force-signin, the “Allow user to close signin modal” do not allow the user to close the login modal by clicking outside the modal, and also hides the close button

Other features which are not present in **force-signin** plugin, but I am hoping to add these in future.’

- I do not show customized modal. Although I was hoping to customize the text.
- I was also hoping to add the topic tracking ( like quora… Do not force signin for few topics etc )

I agree that differences may be minor, and as the guest-gate plugin development started before, it already has users and more votes.

I am planning to use this plugin in two of my discourse sites after it is complete.

Do you feel that differences are minor, and having two plugins doing _almost_ same job will confuse users?

---

<div class="post-metadata">

### Author: ![vinothkannans](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vinothkannans/32/86465_2.png) [@vinothkannans](https://meta.discourse.org/u/vinothkannans)
#### Post date: [April 1, 2017, 5:00pm UTC](https://meta.discourse.org/t/force-signin-plugin/60271/4 "2017-04-01T17:00:23Z")

</div>

> [@net\_deamon](#):
>
> having two plugins doing almost same job

Actually there are three plugins 😉. [Guest Gate](https://meta.discourse.org/t/guest-gate-sign-up-popup-plugin/56625?source_topic_id=60271) plugin is customized fork of my [repo](https://github.com/vinothkannans/discourse-guest-gate). My repo is simple plugin with minimal features.

Now as per @veer’s plugin request I created [Content Lockers](https://github.com/VinkasHQ/discourse-content_lockers) plugin. It have both Guest Locker (Gate) and Social Locker features in single place. Also I am going to add Ad Locker feature in it. (My idea is to create single plugin to all content locking options) 😀

Please have a look at my Content Lockers [repo](https://github.com/VinkasHQ/discourse-content_lockers) too. So you may get more ideas.

> [@net\_deamon](#):
>
> will confuse users?

I hope, It will not confuse users. It will give more options to choose.

---

<div class="post-metadata">

### Author: ![net\_deamon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/net_deamon/32/70126_2.png) [@net\_deamon](https://meta.discourse.org/u/net_deamon)
#### Post date: [April 1, 2017, 5:11pm UTC](https://meta.discourse.org/t/force-signin-plugin/60271/5 "2017-04-01T17:11:36Z")

</div>

> [@vinothkannans](#):
>
> Please have a look at my Content Lockers repo too. So you may get more ideas.

👍

> I hope, It will not confuse users. It will give more options to choose.

I too think the same.

---

<div class="post-metadata">

### Author: ![xiasummer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/xiasummer/32/82790_2.png) [@xiasummer](https://meta.discourse.org/u/xiasummer)
#### Post date: [November 12, 2017, 8:41pm UTC](https://meta.discourse.org/t/force-signin-plugin/60271/6 "2017-11-12T20:41:32Z")

</div>

Actually, I think the raw discourse system has a

**login required** (do not allow anonymous login)

in settings.

So, what is the difference with your plugin?
