Video content can now be included in a course to provide supporting content to a self-paced lab. Vimeo, Wistia and YouTube videos are supported.

Once a video has been added to a course, it can be viewed by clicking the button at the top of the workspace. 

To add video content to a course, see: Adding content to a course - Adding a video

Over the weekend we released the following updates to Heropa. We look forward to your feedback!  

✨ Features

• Pin VMs: We've made it easier to access VMs you work with regularly via a new Pin VM feature. See: Working with VMs in the workspace.
• AWS status check: A tool has been created to help troubleshoot failed connections to AWS VMs. See: AWS VM status check.
• Notify users by email when a new environment is created: Select to notify a user via email when a new environment is created for them. See: Creating and launching an environment.
• Copy content sections: At a section level, content can now be copied and inserted into into other content, making it easier to re-use content. See: Creating content.

🌱 Enhancements

• Events - Classroom thumbnails: Thumbnails are now retrieved directly from the server without requiring local user workspace information. This should result in a significant improvement in the delivery of thumbnails in the Classroom view.
• User session management: Some general enhancements to user session management were implemented to better recycle stale user sessions.
• Deleting a VM within an Environment: When deleting a VM, the name of the VM is now shown to the user prior to deletion.
• Dashboard role permission optimisations: It's now possible to restrict a role's visibility of the Dashboard. See: Using Roles and Permissions.

🔧 Bugfixes 

• Terraform updates are now asynchronous: Updates to existing environments incorrectly showed a failed / rollback status. This was due to the synchronous implementation of Terraform updates to AWS. We have now implemented asynchronous updates, removing the false positive failure status.
• Updating Environments: Row actions available for specific environment states were incorrect and could lead to unwanted actions being available for selection. These have now been updated so only applicable actions based on the environment state can be selected.
• User timeline: For some users, timeline information was not visible in the User Details / Timeline tab due to required data fields being missing. This has now been resolved. 
• Reconnecting to disconnected VMs in the workspace: This was only updating once a successful connection was established, and not showing the attempted reconnection in progress. This has now been resolved.

We've just introduced a troubleshooting tool to help understand the cause of a failed connection to an AWS virtual machine. 

In the Heropa workspace, if an AWS VM is disconnected, you'll now see a 'Status check' button.

Selecting this will run a backend status check, returning vital information from the AWS API to assist in understanding why the VM is disconnected. 

This includes a status check, system and instance checks, and a console screenshot. 

See Troubleshooting VM connections.

Thanks for all your feedback and suggestions on how you'd like for it to be easier to work with multiple VMs in the workspace. 

The result is a new feature where VMs can be pinned to the top of the workspace, making them more accessible and easier to move between those VMs that you work with regularly.

Up to 4 VMs can be pinned along the top of the workspace panel, and remain pinned until they are unpinned.

See: Working with environments in the workspace.

A huge update from our team here at Heropa, with lots of news about what we've shipped recently! 

✨ Features

• Course enrollment email: Select to notify a user via email when they are enrolled in a course. See: Providing users access to a course.
• Company role permission optimisations: We've introduced some granular role permission optimisations for Companies. It's now possible to restrict a role's visibility to their own company only. It's also possible to configure which Company tabs are visible for a role. See: Using Roles and Permissions.
• Record T&Cs acceptance: Company Admins can now configure whether new users are required to accept T&Cs upon user creation. Acceptance is recorded in the user's Profile. See: Configuring user settings in Configuring Company details.
• Content import and export: Export and import JSON content files from Heropa so they can be used in other templates and courses. See: Exporting and importing content. 

🌱 Enhancements

• Events: LTI users can now be assigned seats in Events.
• Direct enrollment in Courses: We introduced a concept whereby Companies need to be assigned access to Courses, to make it easier to enroll users in courses, See: Assigning a Company access to a Course. 
• Adding users to a Company: It's now possible to add a user directly from the Company Details / Users tab. 

🔧 Bugfixes

• Deleting LTI users: A bug preventing deletion of LTI users has been fixed.
• Deleting users in Events: We've fixed a bug preventing users from being deleted in Events.
• Deleting Groups: A bug preventing the deletion of empty Groups has been fixed.
• Public IP addresses: It's again possible to save notes in Public IP addresses.
• Users created via csv import: We were having some issues where new users created by csv import were not being created correctly. This caused access issues for new users. This has now been fixed.
• New users and email domains: We removed the automatic creation of email domains when new users are created as this was causing issues with users being assigned to Companies.
• Templates - Replacing VM images: Searching for VM images was broken. This is now working. In addition, deleted VM images are no longer visible in the list of VM images. 

The Heropa team has been super busy of late. Here's some of the highlights we've been working on over the last little while:

✨ Features

• Events: Add time to an event using the 'Add time' feature. This adds time to all environments in the event and updates the event's end time. See: Running an event.
  
• Events: Save time and effort by configuring an event so that both the event and its participants are automatically deleted when the event finishes. See: Creating an event.
• Templates, Environments: Set one or more secondary IPs on VMs within a template or environment. See: Creating a template.

🌱 Enhancements

• Environments: We previously shared that environments can be protected from deletion. Now, you can also protect individual VMs inside an environment from deletion. See: Managing an environment's VMs.
• Environments: Easily see when environments are due to be deleted via the new 'Deletes on' column on the Environments List screen.
• Templates: When deleting templates, we now show you the template names prior to confirming their deletion.
• LTI: Admins can now configure whether users see an intermediary confirmation screen when joining Heropa from an LMS. Go to Administration / Company Details / LTI to manage this setting.

🔧 Bugfixes

• Events: User initials were displaying in the workspace when their session was idle. This has now been fixed, and they no longer display.
• Environments, Templates: When editing VM networks within an environment or template, we had a bug which was allowing a duplicate IP to be assigned to a VM. This is no longer possible.

We've made some improvements to how role permissions are managed, and hope you like them! 

1. Changes to infrastructure permissions

In the Role / Permissions tab, role permissions can now be set on different infrastructure components in Heropa. Previously, this was managed by an overarching category called 'Infrastructure'. 

This has been replaced by new separate permission categories for Environments, Templates, VM Images, Policies, and Public IPs, example below:

2. A new way to manage what's visible in the left navigation

The new 'Left nav' permission is what determines whether the category is visible in the left navigation menu in Heropa. This can be used to control what screens users with different roles see. Note that there may some roles where permissions to a category might need to be granted, even if seeing the screens in the category is not required for the role. 

For example: You might want to give a role left nav visibility of Courses. If the role also requires visibility of the Environments, Templates and VM images in courses, then a 'View' permission should be set on each of these categories, even if the 'Left nav' permission for these categories is not set. 

Learn more in our knowledge base article: Using roles and permissions.

When creating and editing content to display in the environment workspace, it's now easier for content editors to manage the editing process. A single user can now check out content, effectively locking it for editing. Once their edits are completed and saved, the content can be checked back in. 

If content is checked out to someone who is no longer editing it, there is also the ability to override the check out. 

If you're collaborating on content, be sure to check with the other user before overriding their check out.  

Learn more in our knowledge base article: Editing content.

Admins can now configure their company portal to show up to 4 buttons on the top navigation panel of the portal. 

These can be used to add quick links to other sites such as a knowledge base or support website.  

In Company Details, Configuration tab: 

Once created, the quick link button will be displayed on the top navigation panel of the portal for both admins and end users. 

When multiple versions of an environment are saved as templates, it can be difficult to determine from the VM images list page which images belong to which template. 

We have now added a new feature to allow an admin to add a prefix or suffix to the newly created VM images that are saved back to the VM images collection. 

This should make it easier to manage VM images in different templates.

In Environment Details, select Save as template.

In the Create new template modal, custom VM image names can be created by adding a prefix or suffix, for example:

Original VM image name = DB001
Prefix = V2-
Suffix = -2021
New VM image name = V2-DB001-2021

Adding a custom prefix or suffix is optional. If the fields are left blank, there will be no change to the VM image names.

If there are multiple VMs, then all VM Images created will have the updated names.

Note: The prefix and suffix is only visible in the new VM images collection - the original names are retained inside the new template.