So I believe I’ve uncovered a bug. When bulk enrolling users via the api, it enrolls those users from your root https://xxxx.docebosaas.com domain. If you are using automated groups coupled with enrollment rules to trigger enrollments, that all works well. HOWEVER, if you have a notification that uses a short code, say [course_link], and you want that notification to generate at enrollment into the course, the course link spits back the .docebosaas.com domain, not the extended enterprise in which the users belong. Why? Well, I believe it’s due to the fact that the user who has a connection to the api is logged in at root, thus when the automation (group and enrollment rules) trigger, they are doing so from that root domain.
Why is this a bug? The notification should not be tied to the uploader taking the action, but instead to the location in which the notification is built. I have been offered no workaround or solution to this issue by Docebo support, and have spent a fair amount of time building a flow that takes spreadsheets uploaded in one location and automatically uploads them to the LMS in bulk user management. I’ve come quite some way to hit such an absurd brick wall.