# First-PM notification should not trigger when first login is in a topic

**URL:** https://meta.discourse.org/t/first-pm-notification-should-not-trigger-when-first-login-is-in-a-topic/66362
**Category:** UX
**Created:** [Julho 18, 2017, 8:15am UTC](https://meta.discourse.org/t/first-pm-notification-should-not-trigger-when-first-login-is-in-a-topic/66362 "2017-07-18T08:15:15Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [Julho 18, 2017, 8:15am UTC](https://meta.discourse.org/t/first-pm-notification-should-not-trigger-when-first-login-is-in-a-topic/66362/1 "2017-07-18T08:15:15Z")

</div>

I’ve encountered the following quite a few times:

1. Find a forum I like; start reading a few topics.
2. Land on a topic that I’d like to respond to, so I register
3. After registration I’m redirected back to the topic that I wanted to engage with, but then I get disrupted by our intro-PM:

 ![](https://global.discourse-cdn.com/meta/original/3X/6/c/6c7734f27f95126981d9c17a74848d47e09d8758.PNG)

I already had an action in mind, but now I’m being very strictly instructed to do something else first. More often than not, this has caused me to completely lose my train of thought, and I already know all about this PM and its contents!

To avoid this, how about an exception to the strong PM notification:

> **IF** user is already in a topic upon first-login, **THEN** don’t apply the first-PM overlay.

(Sorry about the convoluted title. Feel free to rewrite it if you can come up with something better.)

---

<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: [Julho 18, 2017, 8:23am UTC](https://meta.discourse.org/t/first-pm-notification-should-not-trigger-when-first-login-is-in-a-topic/66362/2 "2017-07-18T08:23:53Z")

</div>

Is it possible to limit the first PM spotlight effect to when the user is on latest or categories @tgxworld?

---

<div class="post-metadata">

### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [Julho 18, 2017, 8:24am UTC](https://meta.discourse.org/t/first-pm-notification-should-not-trigger-when-first-login-is-in-a-topic/66362/3 "2017-07-18T08:24:45Z")

</div>

There is a bit of a trade-off here: we don’t want to disturb/annoy the user but we also want to make sure that the first message the user receives is the one from discobot… Currently, the way to solve this is via the discobot delay setting.

---

<div class="post-metadata">

### Author: ![tgxworld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tgxworld/32/106117_2.png) [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [Julho 18, 2017, 9:11am UTC](https://meta.discourse.org/t/first-pm-notification-should-not-trigger-when-first-login-is-in-a-topic/66362/4 "2017-07-18T09:11:56Z")

</div>

Shouldn’t be too difficult to not display it on a couple of routes.

---

<div class="post-metadata">

### Author: ![Stranik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stranik/32/85638_2.png) [@Stranik](https://meta.discourse.org/u/Stranik)
#### Post date: [Julho 18, 2017, 9:33am UTC](https://meta.discourse.org/t/first-pm-notification-should-not-trigger-when-first-login-is-in-a-topic/66362/5 "2017-07-18T09:33:46Z")

</div>

It’s not very good, I think. For example, I read, registered and responded immediately. I didn’t read the rules. Missed a letter, bot.