Skip to main content

​
Overview

Once a workflow is created, published, and made public, participants can access it. From here, users can send a booking request (also called an enrollment) to join the workflow.
Bookings are how participants gain access to a workflow’s steps and begin progressing through them.

​
Types of bookings

zyme supports three main types of bookings depending on how the workflow is configured:

​
Normal booking

  • The simplest type of booking.
  • Does not require manual confirmation.
  • Once requested, access is granted immediately, and the user can begin the workflow.
  • Requires payment before the booking is completed.
  • After sending the booking request, the user is redirected to a payment page.
  • Once payment is successful, the booking is confirmed, and access is granted.

​
Confirmation-required booking

  • Some workflows are set to require approval from the owner.
  • After sending a request, the booking remains in pending status until approved.
  • Once confirmed, the user gains access and can start progressing.

​
Login required

To send a booking request, users must be logged in to zyme. This is important because it ensures:
  • Progress through each workflow step is tracked accurately.
  • Feedback, ratings, and uploaded files are linked to the correct account.
  • Workflow owners can monitor client progress and engagement.
If a user is not logged in when submitting a booking request, the platform will prompt them to sign in or create an account first. Once authorized, the booking flow continues seamlessly from where it left off.

​
Booking limits and availability

Workflow preferences may include additional restrictions:
  • Availability windows – Bookings can only be made within specific start and end dates.
  • Limited spots – Some workflows have a maximum number of bookings allowed. Once filled, no more bookings are accepted unless waitlisting is enabled.
  • Waitlists – If enabled, users can join a waitlist once all spots are taken.
  • Private access links – Owners can create special links with usage limits, tokens, or expiry dates for restricted access.

​
What happens after booking

  • For normal bookings: access is granted immediately.
  • For paid bookings: the user completes payment first, then access is granted.
  • For confirmation-required bookings: the owner must approve before access is given.
Once confirmed, the user is enrolled in the workflow and can start progressing through each step.
⌘I