Welcome to our latest edition of the Heropa release notes.

We’re excited to share that the Heropa Public API now gives developers and content teams new ways to manage lab guides and content, provision users, set up event content and check company compute options from their own applications and automated workflows. We've also introduced course archiving, so you can retire a course without losing it.

Plus the team has shipped 11 fixes, 7 of them in Events.

Read on for the details! 

✨ New

• Course archiving. Have a course you’re not running anymore, but might in the future? Administrators can now archive a course and restore it later, keeping all of its contents. Archived courses drop out of your normal course lists and stop accepting new enrollments. Learners already enrolled keep their access, so they can finish their labs. 
• Version history for shared templates. See what changed in a template before you build on it, which matters most when another colleague or team maintains it. Open the version history and change descriptions on any shared template. 

Heropa API

• Lab guide and content management. Content teams and developers can now use the Heropa API to export and import content as JSON, upload images, and manage chapters, sections, pages, exercises and quizzes without completing each step in your portal.  To learn more, read our developer documentation on exporting and importing content in Heropa. 
• User management. Developers can create or update users with their company, role and custom fields already set. Applications can also list the available roles and view details for a selected role. 
• Event content. Developers can create or update an event and assign its content in the same automated workflow, so scheduling systems can prepare events without a separate manual step. 
• Company compute options. Applications can now list the compute options assigned to a company. 

🌱 Improvements

• Single sign-on controls. 
  • A new permission governs who can change a user's single sign-on settings.
  • Companies using OIDC can also choose to refresh mapped details when existing users sign in, so approved changes from the identity provider carry into Heropa at the next sign-in. 
• Event slides. Event hosts can now open the Slides tab whenever slides have been added to an event, even when they are not presenting. Read more on presenting slides in Heropa events here. 

🔧 Fixes

We've got a host of fixes for you this release:

• Event content updates. Changing an event's content now updates its participant environments to match.
• Event lookup through the Public API. Looking up an event by its event code now returns its participant templates, instructors, host seats and participant seats correctly. 
• Event list filters. Filtering events by status or finished state updates the list correctly.
• Shared events. Host and participant environments now launch correctly on their intended separate networks. 
• Temporary event users. Temporary users created for an event are now being removed when the event ends.
• Screen sharing. Learners can reconnect to a shared screen after a brief interruption without the host having to stop and restart screen sharing. 
• Event workspace layout. Event workspaces follow their saved "Open maximised view" setting.
• Single sign-on user details. OIDC claims now populate mapped custom user fields correctly.
• Creating single sign-on users. Administrators can create users with single sign-on enabled from the Users and Companies areas, and through the Public API.
• Participant authentication. API authentication checks follow the settings chosen for participant templates.
• Templates created from environments. Saving an environment as a template keeps its network settings.

Thanks,
The Team at Heropa