> ## Documentation Index > Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt > Use this file to discover all available pages before exploring further. # Manage Subscriber Access to Content Based on Seasonal Start and End Dates Your system must maintain a local cache of entitled subscribers that your Content Management System/OVP solution references when granting subscribers access to seasonal content. The subscribers' access varies based on the specific product purchased, for example, League Play/All Games, Team Play/Games for a specific team. * **Use Case Number:** 2-3-04 * **Completed By:** Software Developer * **Estimated Completion Time:** \<5 days ## Design Approach This use case uses the same design approach as discussed in [Manage Subscriber Access to Subscription Content Based on Their Purchased Subscription](2301_r_manageSubscriberAccessContent#). Vindicia support configures Entitlement Push Notifications in the Subscribe Merchant Configuration to point to an endpoint URL that you provide. Your endpoint consumes the https posts from the Subscribe servers. (See [Configure Subscription Products Based on a Season](2102_r_configureSubscriptionSeasonPortal#).) However, unlike a standard Subscription, the start and end dates for a seasonal Subscription Entitlement are based on the Season Set associated with the Billing Plan for the given Subscription . As shown in the following diagram, for each Season, you can define the number of days before the season start date the subscriber will receive their Entitlement. You can also define the number of days after the season ends the subscriber will remain entitled. On the entitlement start date for the given season, Subscribe issues an entitlement start push notification. You must use a push listener to capture the start entitlement and update the local entitlement cache (see [Manage Subscriber Access to Subscription Content Based on Their Purchased Subscription](2301_r_manageSubscriberAccessContent#)). Likewise on the entitlement end date Subscribe issues an entitlement end notification. You must use that notification to record the end date of the given service. * **[Capture Seasonal Entitlement Start and End Dates Using Push Notifications](../topics/2304_r_manageSubscriptionContentSeasonal#)** **Parent topic:**[Seasonal Subscriptions](../topics/r_seasonalSubscriptions) ## Capture Seasonal Entitlement Start and End Dates Using Push Notifications Contact Vindicia support to configure the Subscribe Entitlement Push Notifications to point to the URL of your push listener endpoint. To manage subscriber access to content based on seasonal start and end dates: 1. Implement a push listener endpoint in your system that is capable of receiving https posts from the Vindicia Subscribe servers. Your authorization system consumes the payload which contains the push entitlement notification message. (See [Manage Subscriber Access to Subscription Content Based on Their Purchased Subscription](2301_r_manageSubscriberAccessContent#)). 2. On the entitlement start date for the given season, Subscribe issues an entitlement start push notification. You must use your push listener to capture the start entitlement and update you local entitlement cache 3. Similarly, on the entitlement end date, Subscribe issues an entitlement end notification. You must use your push listener to capture that notification and update your local entittlement cache to record the end date of the given service. **Parent topic:**[Manage Subscriber Access to Content Based on Seasonal Start and End Dates](../topics/2304_r_manageSubscriptionContentSeasonal#) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.