Notifications
What Vidext shows in your Inbox, the emails it sends, who gets each one, and what you can turn off.
Use this page to know what the people in your organization will be told, and where: in Vidext's Inbox, by email, or both. It helps, for example, before you publish a course to a large team or invite people for the first time.
Vidext only tells people about something that happened and concerns them. There is no marketing message in the product and no way to send a message to everyone.
The Inbox
The Inbox holds your notifications for the organization you are in. Admins and members find it in the sidebar, right under Home; learners find it on their profile card on the Learn page. A number beside it counts the notifications you haven't seen yet. It refreshes every minute and when you come back to the tab, not instantly.
Click a notification to mark it as seen and go where it points, for example the Members page, the course that is now open to you, or the conversation you were tagged in. Mark all as seen clears the count. Notification preferences, at the foot of the Inbox, opens your choices (see Your preferences).
| Notification | Who gets it |
|---|---|
| New course available | The person who can now open a published course, whatever opened it: the course published to one of their teams, one of their teams given the course, or joining a team that has it. A course they could already open through another team does not notify again. |
| You are now an admin / a member / a learner | The person whose role changed. |
| You were added to a team, You were removed from a team | The person added or removed. |
| Name tagged you | The admin or member someone tagged with @ in a chat message. It carries the message and opens the conversation. See Tag people. |
| Someone joined the organization | The organization's admins. |
| Someone is now an admin / a member / a learner | The organization's admins, except the admin who made the change. |
| Someone was removed from the organization | The organization's admins, except the admin who removed them. |
| People added to or removed from a team | The admins of that team, grouped into one notification with how many people and who made the change. |
The person who makes a change is never notified about it. People who arrive through your LMS raise the same notifications as anyone else who joins.
Your preferences
Preferences are personal and apply to one organization. Open them from Notification preferences in the Inbox; admins and members also find them on the Notifications page of their personal settings, which Notifications in the account menu opens.
- People (notifications about who joins, leaves, or changes role, and who is added to or removed from your teams) can be turned off. Only people who receive those notifications see the switch.
- Notifications about your own access (a new course, your role, your teams) and tags can't be turned off.
- Email, under Also notify me by, sends you each notification by email as well, tags included. It is off until you turn it on. New course available stays in the Inbox only, even with email on.
The Notifications settings page also has a Weekly Digest switch. No digest is sent today, so it has no effect.
Emails
Besides the notifications you can choose to get by email, Vidext sends these emails. They are always sent and can't be turned off.
| When it goes out | |
|---|---|
| Sign-in code | Someone signs in with their email. |
| Welcome | A person signs in for the first time. Sent once, shortly after. |
| Added to an organization | An admin adds someone who already has a Vidext account: they are added straight away, with no invitation to accept. |
| Team invitation | Someone is invited by email to your organization or to a team. |
| Invitation reminder | Someone uses Resend on a pending invitation, or adds a person who was already invited and doesn't skip them. There are no automatic reminders. |
| Join request | Someone asks to join your organization. Sent to its admins. |
| Join request decision | An admin approves or denies a join request. Sent to the person who asked. |
| Course enrollment | A learner is enrolled in a course: when the course is first published to their team, when their team is assigned to a course that is already published, or when they join a team through an invitation or are added to it. One email per enrollment, opening the course's first live module. |
| Certificate ready | A learner is issued a certificate, usually right when they complete a course that issues them. Carries the link to the certificate. See Certifications. |
| Billing notification | A billing event happens on the organization's subscription, such as a plan change, a cancellation, or a failed payment. Sent to admins. |
Some things deliberately send no email:
- Publishing an update, withdrawing or restoring a module, unpublishing a course, and publishing it again. Learners who were already enrolled are not emailed again.
- Enrollments that come from joining the organization on your own — through domain join, an approved join request, or being added by an admin — which put someone in your organization's default team. They are enrolled in its published courses, but get no course email.
- An enrollment in a course that has no live module at that moment. Its learner is not emailed when a module of it goes live later either.
- Being added to a conversation from the Share panel. Only a tag in the chat can send an email, and only to someone who turned email on.
Delivery
Emails are queued with automatic retries and fall back to a second provider if the first one fails. Bulk events, like assigning a course to a large team, are sent in batches, and when some emails can't be sent the screen says how many rather than dropping them silently.
No learner nudges
Reminders for learners ("you haven't finished X") are not part of the product. The enrollment email is the delivery touchpoint.
Last updated on