# Telegram - authorised/unauthorised users

**URL:** <https://discourse.nodered.org/t/telegram-authorised-unauthorised-users/15100>\
**Category:** General\
**Created:** [4 September 2019 12:38 UTC](https://discourse.nodered.org/t/telegram-authorised-unauthorised-users/15100 "2019-09-04T12:38:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [4 September 2019 12:38 UTC](https://discourse.nodered.org/t/telegram-authorised-unauthorised-users/15100/1 "2019-09-04T12:38:41Z")

</div>

I'm finally trying out Telegram (using node-red-contrib-telegrambot ) and I've set up a bot and using receiver node to get messages from my mobile phone.

The rx node as two outputs - one from authorised user and from non-authorised

Mine are appearing on non-authorised

Does this mean anyone with who knows name of my bot could send it messages?

How do I get my messages to be authorised?

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [4 September 2019 12:47 UTC](https://discourse.nodered.org/t/telegram-authorised-unauthorised-users/15100/2 "2019-09-04T12:47:55Z")

</div>

> **[User Authorization](https://core.telegram.org/api/auth)**
>
> Authorization is associated with a client’s encryption key identifier: auth\_key\_id. No additional parameters need to be…

---

<div class="post-metadata">

**Author:** ![rholmesa](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rholmesa/32/29252_2.png) [@rholmesa](https://discourse.nodered.org/u/rholmesa)\
**Post date:** [4 September 2019 13:02 UTC](https://discourse.nodered.org/t/telegram-authorised-unauthorised-users/15100/3 "2019-09-04T13:02:56Z")

</div>

Authorised includes those with 'chatid's specified when you set up the Telegram Receive Node.

I have only just discovered that myself.

Consequently you can ignore messages from the second output if you have specified a chatid as 'authorised' as they will appear from the first output.

Hope this helps

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [4 September 2019 21:46 UTC](https://discourse.nodered.org/t/telegram-authorised-unauthorised-users/15100/4 "2019-09-04T21:46:10Z")

</div>

Yes, and that is a nice way to add some additional security to your bot - assuming that you know who might need to interact with it. Personally, I would attach a small flow to the unauthorised side to capture/log unknown chatids which makes it easy to add new ones to the authorised list just by getting, say Mrs Cymplecy, to send a message to the bot.

---

<div class="post-metadata">

**Author:** ![windkh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/windkh/32/4713_2.png) [@windkh](https://discourse.nodered.org/u/windkh)\
**Post date:** [29 March 2020 20:40 UTC](https://discourse.nodered.org/t/telegram-authorised-unauthorised-users/15100/5 "2020-03-29T20:40:31Z")

</div>

Version 7.2.0 allows to control the usernames and chatids that are authorized from within the flow.