With Advanced Access Manager 4.6 or higher you have the ability to grand access to your website content for limited time frame. For example you allow you visitors to see certain page only until next Monday or January 1st 2pm. The short video below shows this neat feature in actions.
You are required to enter only expiration criteria which can be any valid date/time format. If you are not tech savvy person, please do not get intimidated by this requirement. Technically it means that you need to enter English string that will be translated into some date and time in the future.
For example if you want to have expired access to your post in 5 days, you can simply enter +5 days. The same way you can say seconds, minutes, hours, days, weeks, months or years. You can even enter next Tuesday if you want to have access expired that day.
It is also easy to set specific day or the year or even hour. For example May 13, 2017 2:30 pm or 03/04/2018. However be aware that dates in the m/d/y or d-m-y formats are disambiguated by looking at the separator between the various components: if the separator is a slash (/), then the American m/d/y is assumed; whereas if the separator is a dash (-) or a dot (.), then the European d-m-y format is assumed. If, however, the year is given in a two digit format and the separator is a dash (-, the date string is parsed as y-m-d. To avoid potential ambiguity, it’s best to use ISO 8601 (YYYY-MM-DD) dates.
As soon as you entered expiration criteria, AAM monitors access to selected post or group of posts in realtime. No further monitoring on your end is required.
By default, when access expired, AAM will swap access settings and restrict access to selected post or group of posts by checking READ option. This behavior can be modified with ConfigPress option post.access.expired option. For example instead of restricting access to expired post, you might want to limit access with LIMIT option.