EchoVideo

Currently, any EchoVideo Administrator can grant Administrator access to other users. Whilst institutions can establish internal governance processes around administrator access, these ultimately rely on trust, as once a user is granted Administrator access, they can elevate other users as admins without oversight or approval from the system owners. We would like the ability to restrict this capability to a designated subset of trusted users only, either through a dedicated "Super Administrator" role or a granular permission that controls whether an Administrator can assign Administrator privileges to others. This would provide stronger access governance, support least-privilege principles, and reduce the risk of unauthorised privilege escalation while still allowing administrators to perform their day-to-day operational responsibilities. This feature request is different though would be a great value add in addition to https://echo360.canny.io/echo360-feature-requests/p/custom-role-types

As an admin I would like to be able to see my user's LTI 1.3 connections within EchoVideo. I would also like to be able to remove connections for users from the admin UI as well. This would be great for troubleshooting and general testing.

In EchoVideo, currently, as soon as the study aid materials are generated by AskEcho, they are publicly available to students. We would like a human decision in the middle of the content generation and the public availability of the content. We can't implement AskEcho, from an institutional policy perspective, until this update is in place.

While testing individual sharing, a video was shared with a student who was then able to modify the media title and AskEcho content. In many instructor-to-student sharing scenarios, the intent is to provide access to view or interact with the media, not to modify its metadata or AI-generated content. This creates a risk of: * Accidental modification of media titles and descriptions * Unauthorised changes to AskEcho content * Confusion around ownership and content integrity * Additional support overhead when shared content is altered unexpectedly Proposed Solution When sharing media with an individual, provide an "Allow Edit" toggle that can be enabled or disabled by the content owner. When "Allow Edit" is Enabled Recipients can: * Edit media title/name * Edit descriptions and metadata * Modify AskEcho content * Perform any other existing edit actions permitted by current sharing rules When "Allow Edit" is Disabled Recipients can: * Access and view the shared media * Use permitted playback and engagement features Recipients cannot: * Change the media title * Edit descriptions or metadata * Modify AskEcho content * Make any content-level changes Example UI Options Option 1: Toggle Within the Share Dialog Add an Allow Edit toggle directly to the "Share with an Individual" dialog before the user clicks Done . Benefits: * Permission is configured at the time of sharing * Easy to understand * Consistent with existing sharing workflows Option 2: Per-User Permission Control Display an Allow Edit toggle beside each individual user in the sharing management screen. Benefits: * Permissions can be adjusted after sharing * Different users can have different levels of access * Provides greater flexibility for instructors and administrators Expected Benefits * Greater control over shared content * Protects media metadata and AskEcho content from unintended changes

When someone is a Delegated (Designated) Admin, they should not have full control over Users. At present, a Delegated Admin (DA) can elevate an existing User to an DA role, as well as remove a User from their DA role. This should only be controlled by a Admin will full rights across the tenant, and it's a security issue to have this loophole in place.

Currently, when an EchoVideo video is embedded in an LMS in our case Moodle (either via the embed tool or using embed code), there is no option to disable the download feature. This results in a download button being visible to end users, allowing videos to be saved locally. This has raised concerns among some staff, particularly around intellectual property and the potential for videos to be downloaded and redistributed without consent. While we recognise that the ability to download videos can be useful in certain contexts (e.g. video assignments where markers or external examiners may need offline access), there is currently no flexibility to control this behaviour based on use case. Requested Enhancement: We would like the ability to: Disable downloading at the point of embedding a video, and/or Modify download permissions after embedding (e.g. via settings or media management) Use Cases: Teaching staff embedding lecture or teaching content where redistribution should be restricted Courses with sensitive or licensed material Maintaining download access for assessment workflows where required Impact: Providing this control would give educators greater confidence in using embedded video, improve content security, and support a wider range of teaching and assessment scenarios.

We have a use case where a particular set of videos should have an alternate retention/archive/deletion policy than other videos.

Please provide functionality equivalent to what was available in the atto plugin (LTI1.3 support) for the TinyMCE in Moodle.

Currently, the editor can open before processing is complete and may appear empty or incomplete until the user manually refreshes or reopens the presentation. Expectation is that once processing completes, the editor should automatically re-fetch and display the uploaded content, remove loading states, and allow editing without requiring any user action. (as in uploading in a "new presentation" This would reduce user confusion, prevent failed-upload assumptions, and improve the presentation upload/editing experience.

We currently have a default player style that includes bump-in and bump-out videos to meet our university’s copyright requirements. This player style is set as the default within our EchoVideo environment to encourage staff to use the correct player when creating and uploading media for our Learning Management System. While this setup works well for teaching materials, we’ve encountered an issue with student video assignments. When students submit videos via the EchoVideo student assignment submission media picker, the system applies the default player style—resulting in our university’s copyright branding appearing on student-created content. What we need is a way to assign an alternate player style (one that is not the default) specifically for student submissions. This would ensure that student-generated content is displayed without university copyright branding while maintaining the correct setup for teaching and learning materials.