What does the "Send notification" column in the User page mean?

Hi ​@vhung ,

That column is a global master toggle for the individual user account. Essentially, it controls whether or not the system is permitted to send system-generated notifications (like enrollment confirmations, course due dates, or digests) to that specific user.

If you set it to No, the platform completely stops triggering notifications for that user, acting as an absolute override to any rules you have active in the Notifications app.

How this plays out in real-world administration: In enterprise environments I work with, we typically rely on this flag for two main reasons:

1. Protecting the C-Suite: We often turn this to No for C-level executives, co-founders, and senior stakeholders. They might need to be enrolled in global or compliance courses for tracking purposes, but they absolutely do not need automated LMS push notifications cluttering their inboxes.

2. Test Accounts & QA: When setting up "dummy" user profiles to troubleshoot or audit new learning paths, we keep this toggled to No so our testing sprints don't accidentally trigger a flood of email alerts.

If you want to dive deeper into how the platform evaluates these rules, the Docebo Notification app documentation covers the logic framework well.

That's interesting!

In our environment, I see that it is set to NO for all users but I can confirm that they do get enrollment notifications. 

I'm pretty sure this column only indicates if the system sends the Welcome Notification (User has been created).

Spot on, ​@Ziv ! You are 100% correct, and I completely crossed my wires there. Thank you for the course correction and for keeping the record straight!

You are absolutely right—the "Send notification" option (whether toggled on the UI or mapped via CSV user import) is strictly a one-time action trigger. It solely dictates whether the platform will immediately fire the "User has been created (by administrator)" notification (the classic Welcome Email) the exact moment the account is provisioned. As you accurately pointed out, it is not a permanent master suppression switch, which is why your users are still properly receiving their transactional course enrollment emails.

In one organization I worked with, we actually built an external notification system using Docebo Connect and used the send_notification field as a tool to prevent sending native platform emails to specific people we didn't want receiving them, which is exactly where my confusion came from.

Thank you again for catching that slip! For anyone diving into the exact properties of user provisioning, the official breakdown of this specific creation field can be found directly in the Docebo Help Center Guide on Creating and Managing Users.