Because the Library Bundle has criteria on recent activity and block status, users can cease to be eligible for access. We have a daily cron job which updates user information, in addition to updating on user login. If a user logs in to the platform they'll see right away that they don't have access, and using the current homepage design, will see why. If they become ineligible via the regular cron job, however, we should email them to let them know.

If they are no longer eligible due to recent activity, we should tell them what our data is on that (e.g. "you only made 5 edits this month") and encourage them to edit. If their block status changed, we should request that they contact us for review.

This doesn't need to be a launch priority because it doesn't become a potential issue for 30 days after launch.

Open questions

• Should we email users when they stop being eligible because of lack of recent activity, or block status changes, or both?
• How do we avoid spamming users who might be eligible and not over time?
  • We could only email one update until the user logs in again.
  • We could add a user preference to turn off these emails