Skip to main content
All CollectionsAccesses
Product Launch - Setting a Fixed Launch Date in Access
Product Launch - Setting a Fixed Launch Date in Access

product launch, accesses with start date

Updated over a week ago

In this article, we explain the product launch feature.

For each member who receives this access, the start date for all courses is set to a specific date. This allows you to schedule a product launch in the future or to unlock all modules in a course for members even though scheduled content release (drip) is available.

This works by setting the launch date to a date in the past. The "New section unlocked" messages will not be sent.

The graphic above shows 3 states:

  1. If you do not set a fixed launch date: All new members always start with the launch date at the day the member gets access to a course for the first time. If the member buys a course today, the course starts today. The time delayed drip content starts from this date.

You can adjust this date later. Refer to the screenshot and the help article on member administration.

2. You set the date in the past. This makes content that would otherwise only be released on a delayed basis available earlier. Example:

Today is 15/03/2021. I set the date to 01/12/2020. The online course is a 12-week programme in which another chapter is unlocked every 7 days. As week 1 is available immediately, the last chapter becomes available 11 weeks after the start date.

In this example, all content would already be available to the member today on 15/03/2021. If you set the date only 10 weeks in the past, the last chapter would not be available yet.

If you set the date for one access in the past, then you can assign a course in 2 ways. Once with drip content and once without, and you can assign both accesses automatically.

The email "New chapter unlocked" for content that was unlocked in the past is discarded so that you don't accidentally send every member +10 emails at the same time.

Product Launch Feature

The 3rd option is to set the date to a date in the future. This gives you the possibility to plan an online course/coaching launch / an x-day challenge.

This is how the states of the sections behave depending on the start date:

Section State

Behaviour with launch date set in the future

Always visible. Regardless of the set launch date.

Available 7 days after launch date.

Available 7 days before launch date. You can simply enter a negative value to represent your pre-launch phase (countdown).

Available 7 days before the launch date. You can simply enter a negative value to represent your pre-launch phase (countdown).

If you enter a delay of 0 days, the content is available from the launch date, which is also reflected in the status indicator of the section.

In the example above, you want to launch in 4 weeks from today. On April 15th content with the status "Published" is always visible in the members' area. For instance, this could be a welcome video. "Welcome to the launch of the x Days Challenge".

Before the launch, e.g. 08.04. you want to release a section. This is the pre-launch phase. Here, you simply set -7 days for the drip content. Your members will be informed about the new content as usual via the system email.

On the launch date, you set the delayed activation to 0 days. This means that the content will be available on this date.

After the launch date, the Drip contents will continue to work as usual.

Important information:

Just as with the expiry date of the access, the launch date is set for each member when the access is granted. A later adjustment of the date in the access does not change the data in the individual members. The access works as a template. Adjustments to the date are not applied to members with this access.

If a member has already had access to a course or has had access once, then the launch date that was set the first time is always set for this member. If you test the launch date function again and again with the same member, then the first launch date is always displayed and the date of the product launch is not entered as the launch date.

Did this answer your question?