Enhanced Reader Activation & Status Management
backlog
V
Vijay Sakthivel
Bulk Resend Activation Emails
Currently, there is no option to bulk resend activation emails to readers who have not activated their accounts. Customer needs the ability to select multiple readers and trigger activation emails in bulk.
Send a notification email to the readers
We do not have the option to send a notification email to the non-signed-in users for now. It will be good to have an option for better adoption.
Improved Export Data for Reader Status
In the current export, the Last Login Date field is blank for non-activated users and for those who have activated but not signed in yet. Customer prefers to see the explicit status (e.g., “Hasn’t signed in yet” or “Not activated”) reflected in the exported data to easily distinguish between these cases.
Log In
D
D360 Product Management
marked this post as
backlog
Mohamed Shakheen
Hi Kiwi Giraffe Vijay
Thank you for sharing these valuable suggestions - those are indeed interesting asks. We understand how features like bulk resend of activation emails, notification emails for non-signed-in readers, and improved reader status export data could streamline reader management and improve adoption.
At the moment, these enhancements are not part of our roadmap, and we’ve observed limited customer traction around similar requests. We’ll continue to monitor additional feedback and upvotes, and will revisit these ideas for future roadmap consideration based on broader customer demand.
For now, we’ve moved this item to our backlog for tracking and visibility.
Appreciate your understanding and continued support in helping us shape the product.
K
Kiwi Giraffe
Mohamed Shakheen
Thank you for the update and for moving this item to the backlog for visibility.
That said, I have to admit I’m surprised these enhancements aren’t on the roadmap. From a technical perspective, these seem like relatively light to moderate lifts that build on existing functionality. Bulk resends would reuse the current activation email logic, improved export data would extend the existing schema, and reader notifications would rely on standard event tracking or inactivity triggers, all common patterns in SaaS platforms.
Given the potential impact on user adoption and administrative efficiency, these appear to be high-value, low-complexity improvements. If other customers haven’t raised them yet, that’s even more surprising, especially since larger organizations would likely face far greater challenges managing reader engagement at scale.
I hope the team will consider revisiting these sooner rather than later, even incrementally, given the clear usability and adoption benefits.
V
Vijay Sakthivel
Raised on behalf of Kiwi Giraffe