Now that you've scheduled a training event, it's time to invite your learners. This takes place outside of the Strigo environment.
Strigo provides you with the invitation details you need to easily manage the RSVP process. You can either copy and paste the invite details directly from the UI, or use our APIs to automate this process, using your current LMS or CRM application.
This article explains what information should be shared in your invitations as well as the process of joining the event.
Private events
For private events, your invitation should include these items:
Start date and time
Event link
System compatibility test link (Test link, also available in a longer-form help article)
We’ve streamlined the process for learners. When they access the event link, they must create a learner ID using their email address. Learners will not receive a confirmation email.
In the background, Strigo then checks this email address against the whitelisted emails you added to the event to verify the enrollment. Once confirmed, a learner will be taken straight to the classroom, as soon as the host starts the event.
Public events
For Public events, your invitation should include these items:
Start date and time
Event link
Access token
System compatibility test link (Test link, also available in a longer form help article)
We’ve streamlined the process for learners. When they access the event link, they must create a learner ID using their email address. Learners will not receive a confirmation email.
Once the host starts the event, learners must enter the access token in order to enter the classroom.
Retrieving the event information
You can copy and paste the information for both private and public invitations from the event's Summary Page.
This page can be accessed in one of two ways:
When you finish editing your event and hit the “Schedule Event” button - you will be automatically taken to the page
Visit the Events page and click the desired event from the list
Alternatively, this information can also be retrieved using the Event Resource from Strigo's APIs