Overview
Notification preferences are stored per workspace member. Event toggles decide what activity qualifies, while channel toggles decide where that qualifying activity is delivered.
- Keep a complete in-app operational feed.
- Enable private Telegram delivery for urgent events.
- Send selected activity to the account email.
- Understand that channels and events are independent controls.
Before you start
- An active Telestars workspace membership.
- At least one connected bot with a Telegram username when enabling Telegram delivery.
- A valid account email when enabling email delivery.
Step by step
- Open Notifications and select Channels in the left navigation.
- Leave In-app enabled when you want events retained in the dashboard bell and unread workflow.
- To use Telegram, select a connected agency bot and complete the private connection flow before the switch can stay connected.
- Enable Email to send qualifying alerts to the email address on your Telestars account.
- Open Events and disable categories that should not be delivered through any enabled channel.
- Generate a permitted test event and verify delivery in every selected channel.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Per-user settings | Channel and event preferences are stored for each user inside the active organization. |
| In-app | In-app delivery populates the dashboard bell and its read-state workflow. |
| Telegram | Telegram delivery requires both a selected connected bot and a private Telegram user ID established by the connection link. |
| Email goes to the signed-in account address and is throttled by event type to prevent repetitive bursts. | |
| Two-layer filtering | An event must pass its event preference and the destination channel must be enabled before that channel can receive it. |
Verify the result
- The Channels summary shows the expected number of active destinations.
- Telegram displays Connected privately through the selected bot when enabled.
- A test event appears only in the channels you chose.
Troubleshooting
| If you see this | What to check |
|---|---|
| A channel is on but nothing arrives | Check the Events tab for the specific event toggle and confirm your role or assignment can receive that bot-scoped activity. |
| Email goes to the wrong address | Notifications use the current Telestars account email; update the account identity rather than entering an address on this page. |
| Telegram switch does not remain connected | Select a bot with a Telegram username and finish the opened /start flow before the temporary connection wait expires. |
Best practice
Keep in-app alerts enabled as the audit trail, then add Telegram or email only for the events that require attention away from the dashboard.