Skip to content
English
Sign in
Contact us
  • There are no suggestions because the search field is empty.

Controlling Student Access Before Go-Live

When to use this article
Use this article when preparing to open your VZ system for a new season and you need to ensure students cannot log in before your official go-live date and time. This guide explains how to manage imports, start dates, and VZ system lock settings to prevent early or unintended access.

Learning Objective

By the end of this article, you should be able to:

  • Identify all guardrails that control when students can access VZ.

  • Coordinate import timing and start dates to align with your launch plan.

  • Request VZ to configure lock-before and lock-after settings to secure your system window.

Step-by-Step Guidance

1. Plan Access Timing During Archive

  • Notify your IT or data team to pause automated imports once the system is archived.

  • Determine your go-live date and time.

  • Decide when imports should resume and whether you’ll need a post-launch lock-after window (for example, to close access after hours).

2. Configure Start Dates in Pre-Production

  • Review and update Task List item Start Dates to match your go-live date and time so items appear only when the system opens.

  • Review Communication Configurations and confirm all start dates are on or after go-live.

  • Review Event or Reservation start dates to ensure students cannot register early.

  • Test these settings in pre-production with a test student to confirm access is correctly restricted.

3. Request Lock Settings from VZ

Submit a support ticket requesting VZ to configure your preferred lock settings:

  • Lock-Before: Prevents any student logins until a specific date and time.

  • Lock-After: Re-closes student access automatically at or after a specific date and time (optional).

💡 Both settings can be configured in pre-production and will automatically carry to production during push-to-production.

4. Validate After Push-to-Production (Recommended ~1 Week Before Launch)

  • Confirm lock settings are active in production.

  • Import or create a test student and verify:

    • Login is blocked while Lock-Before is active.

    • Task List items and Communications are not visible before go-live.

5. Go-Live Day

  • Ensure Lock-Before expires at the planned time.

  • Resume imports if they were paused.

  • Test with a student account to confirm successful login and visibility of intended items only.

6. Optional Post-Launch Actions

  • If access needs to be paused or delayed after launch, VZ can apply a Lock-After date/time.

  • When ready, VZ can remove or adjust this lock at your request.

Check Your Work

✅ Confirm imports are paused during setup and resume on schedule.
✅ Verify start dates for Task List items, Communications, and Events align with your launch time.
✅ Test access in both pre-production and production using a test student.
✅ Ensure lock settings activate and expire correctly.

Common Pitfalls & Tips

⚠️ Imports restarting early: If your IT team resumes imports too soon, students may gain access unexpectedly. Confirm timing before go-live.
⚠️ Start dates misaligned: Items or communications with old start dates can appear early—review all before push-to-production.
💡 Always test in production: Even if pre-production testing is successful, a quick validation in production ensures no sync or copy errors occurred.