For whoever owns the training calendar
Training sent as a bare calendar invite gets accepted out of politeness and then ignored. Give it a page with the agenda, two questions about the person signing up, and reminders before the hour.
The reason staff training gets skipped is that nobody ever had to read anything. An invitation lands in the work calendar, the entry says forty-five minutes on a Thursday, and declining simply means not turning up. What changes that is not a louder subject line but a page: what is covered, in what chunks, by whom, how long it runs, and where the person says they are coming.
A webinar page in My Joyfullday is a registration page for one live session, and internal training suits it well. You publish it, send the link once into the company chat or the internal mail you already use, and colleagues sign up with their name and email. There is nothing new for them to install and no account to make, which matters when your audience already has eleven tools to ignore.
Each chapter holds its own duration and a line on what the attendee takes from it, so a policy update reads as three short segments with an end rather than an hour of someone talking.
A speaker section keeps the name, job title, photo and a short biography. For internal sessions that line is often what makes people treat the training as real.
The time zone shows as a label beside the start time, chosen by you. Write it once and remote staff stop doing arithmetic in their heads.
Cap the places to what you can genuinely hold. The page can show how many are left, and says it is full once they are gone.
Registration collects a name and an email. Extra fields are yours to add, and for a training session two are usually enough.
Once the hour has passed, the job is a list. The dashboard keeps every registrant with a status — registered, attended, waitlisted, cancelled, no-show — and exports the whole thing as CSV or PDF, so the file goes to whoever maintains the training record. You mark who turned up; the export carries that out. Nothing here generates a certificate, and if your process needs a signed record, this roster is what feeds it rather than the record itself.
Between the sign-up and that export sit the reminders: emails at twenty-four hours, one hour and fifteen minutes before the start, to everyone registered unless you switch them off. After the session you can broadcast a message to a chosen slice of the registrant list, which is the natural place for the slides link or the follow-up reading.
Two limits decide whether the setup works for you. The first is that one page is one session. There is no repeating entry behind the link, so a monthly training slot needs a page per date. That is lighter than it sounds: the second page reuses the agenda you already wrote, and the first page's registrants are the obvious first audience for it.
The second is that you bring the meeting. The join address and the platform name are fields you paste in, and the platform can be whatever you present on. Nothing here creates a meeting or reaches into one. The page does the invitation, the sign-up, the reminders and the list, and hands the room over to you.
How it works
Date, start time, the zone label, how long you intend to talk, and who is speaking. Build it in the web app, or message Jitabi those lines and let it draft the shape of the page.
Three or four segments, each with a duration and a sentence on what people take from it. This is where the point of the training belongs, in words your colleagues actually read.
Department and role, a place limit that matches the room, and a waitlist behind it if you want one. The page will say how many places are left while they last.
Post the address where staff read. Reminders run themselves, attendance gets marked as replies come in, and the finished list exports as a file for whoever keeps the record.
Questions
No. A page is a registration page for a single session, so each date needs its own page. Hosts usually reuse the same agenda text, and the previous registrant list is the first group you send the new page to.
It shows the names and emails that registered, and whatever you asked for as custom fields, so a department column is there if you ask the question. Reading it across teams is your side of the work rather than a report we generate.
Each attendee registers with their own name and email, because the access link that arrives in the confirmation belongs to that person. Asking a manager to sign up twelve names would leave twelve people without a way in.
Not directly. Messages go to segments of the registrant list, so the people who did not register are outside it. For those names the honest route is their own manager or the team chat that carried the link.
They email the registered attendees only, at twenty-four hours, an hour and fifteen minutes before the start. If you would rather not send them at all, you can switch the reminders off before the session.
Get Started
Put the agenda, the speaker and the length on a page, ask two questions, and cap the room. Then let the reminders and the export do the rest of the week's work.
