# User Invitation/Poking a user to a topic is now live!

**URL:** https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180
**Category:** Feature
**Created:** [04.Апрель.2015 00:27:03 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180 "2015-04-04T00:27:03Z")
**Posts on this page:** 11
**Page:** 4

<div class="post-metadata">

### Author: ![thomaspurchas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thomaspurchas/32/115664_2.png) [@thomaspurchas](https://meta.discourse.org/u/thomaspurchas)
#### Post date: [16.Апрель.2015 23:25:32 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/61 "2015-04-16T23:25:32Z")

</div>

Thanks for this! It makes this feature way more useful 😃

But a couple of thing (I’m really sorry about this), I can’t seem to invite entire groups (my site uses SSO and I’m an admin, not sure if thats important), even on non-private topics groups are not appearing in the search/username box. Nor can I enter more than one username into the invite box.

Also for group invites, could group selectability be defined by the groups alias settings. i.e. If I’m a member for GroupA, and GroupA’s alias setting is “Only group members, moderators and admins” or similar, then I can always invite that group, regardless of my trust level / admin status.

---

<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: [17.Апрель.2015 02:27:45 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/62 "2015-04-17T02:27:45Z")

</div>

Groups are not supported for invites at this time. Would be kind of risky.

---

<div class="post-metadata">

### Author: ![thomaspurchas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thomaspurchas/32/115664_2.png) [@thomaspurchas](https://meta.discourse.org/u/thomaspurchas)
#### Post date: [17.Апрель.2015 09:00:44 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/63 "2015-04-17T09:00:44Z")

</div>

Why are group invites more risky than group @mentions?

Both create a notification and an email, if anything invites are less risky because there rate limited unlike @mentions.

---

<div class="post-metadata">

### Author: ![elberet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elberet/32/122404_2.png) [@elberet](https://meta.discourse.org/u/elberet)
#### Post date: [17.Апрель.2015 14:29:07 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/64 "2015-04-17T14:29:07Z")

</div>

Awesome!

Shouldn’t it now be quite easy to also implement the [“create only” security setting](https://meta.discourse.org/t/new-category-permission-create-and-see/12053/18)?

Simply allow users to create a new topic in the restricted category and be implicitly invited to the topic they just created…

* * *

> [@thomaspurchas](#):
>
> Why are group invites more risky than group @mentions?

Because a TL2 user could expose a private topic to the world by inviting the `trust_level_0` group.

---

<div class="post-metadata">

### Author: ![thomaspurchas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thomaspurchas/32/115664_2.png) [@thomaspurchas](https://meta.discourse.org/u/thomaspurchas)
#### Post date: [17.Апрель.2015 15:17:49 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/65 "2015-04-17T15:17:49Z")

</div>

> [@elberet](#):
>
> Because a TL2 user could expose a private topic to the world by inviting the trust\_level\_0 group.

Please read the thread. This feature **does not grant permissions**.

> [@thomaspurchas](#):
>
> That’s what I thought this feature was, an @mention without the need to create a post, or munge a name into a sentence.

> [@codinghorror](#):
>
> That is what it is. People are trying to pervert it into a permission grant.

---

<div class="post-metadata">

### Author: ![elberet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elberet/32/122404_2.png) [@elberet](https://meta.discourse.org/u/elberet)
#### Post date: [17.Апрель.2015 15:35:35 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/66 "2015-04-17T15:35:35Z")

</div>

Hum. You’re right, sorry. I totally misinterpreted the change to `lib/guardian.rb`.

Too bad, this also invalidates the idea regarding create-only categories. ☹

---

<div class="post-metadata">

### Author: ![thomaspurchas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thomaspurchas/32/115664_2.png) [@thomaspurchas](https://meta.discourse.org/u/thomaspurchas)
#### Post date: [20.Апрель.2015 20:25:06 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/67 "2015-04-20T20:25:06Z")

</div>

Sorry to poke you like this @codinghorror, but I was hoping to get your opinion on this:

> [@codinghorror](#):
>
> Groups are not supported for invites at this time. Would be kind of risky.

> [@thomaspurchas](#):
>
> Why are group invites more risky than group @mentions?
> 
> Both create a notification and an email, if anything invites are less risky because there rate limited unlike @mentions.

---

<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: [20.Апрель.2015 23:22:44 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/68 "2015-04-20T23:22:44Z")

</div>

Group mentions needs to be redone before we’d attempt group invites.

---

<div class="post-metadata">

### Author: ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [26.Апрель.2015 04:43:06 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/69 "2015-04-26T04:43:06Z")

</div>

So, I run a closed discourse.. I normally tell people I’m going to invite them, then would visit my preferences and invite them.

The invitations they get from within a topic are WAY more interesting than normal. very cool..

It makes me want this [feature implemented](https://meta.discourse.org/t/link-to-new-user-after-invite-is-accepted/26501) even more though… but I find my invites are being accepted more frequently, and I need to visit my invites page less often in general. AND they are already activated, which is double prizes.

Thanks again for this method of inviting people.

---

<div class="post-metadata">

### Author: ![jesselperry](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jesselperry/32/119501_2.png) [@jesselperry](https://meta.discourse.org/u/jesselperry)
#### Post date: [01.Июнь.2015 14:10:38 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/70 "2015-06-01T14:10:38Z")

</div>

I like this feature because it allows you to privately invite someone to a topic, without calling them out publicly and awkwardly forcing them to respond.

One idea although probably not trivial to implement - being able to email reply-to the invite to respond to the topic. Reduces friction even more, especially since you’re probably inviting someone that isn’t that engaged with the Discourse to begin with.

---

<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: [10.Июнь.2015 20:22:43 UTC](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180/71 "2015-06-10T20:22:43Z")

</div>



[Previous page](https://meta.discourse.org/t/user-invitation-poking-a-user-to-a-topic-is-now-live/27180.md?page=3)
