Make it easy to configure LTIs and reuse settings

[jmakowski1123]

At-A-Glance

For instance and platform administrators, it should be easy and non-technical to configure third-party apps for use across the instance. The technical set up should only be required once per instance/platform, after which org level enablement should be non technical. This is the step at which a license (key and secret) can be entered, and access enabled.

For authors and course teams, the process of choosing which pre-configured apps to use in a course should be easy and non-technical.

For learners, the process of engaging with an LTI tool should be straightforward and only require permissions for authentication once. User permissions around LTI should be stored and tagged to the user account, and ideally should follow the user from course to course to enable a unified experience. Furthermore, user settings should be saved for as long as a user’s account exists or until the user requests a change.

More information

Product specs

• Product spec: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3903979521/Phase+1+LTI+Workflow+Enhancement

Design files

• Lofi concept frames: https://www.figma.com/file/lDNWHrVDYSoPk6yy1MP6x4/LTI-Tools---Low-Fi-Wireframes?type=design&node-id=0-1&mode=design&t=QFuhc49yuhfmNWlx-0

Kanban board

• https://github.com/orgs/openedx/projects/58/views/1

Key Epics

#143

Stakeholders

Primary Contributors

• edX (product)
• Axim Collaborative (product and coordination)
• OpenCraft (designs)
• edunext (usability testing)
• Pearson (backend contributions)

Community release milestones

• Quince: Reusable configuration for 1.3 available on the backend

• Redwood: Target MVP release user-facing UX/UI

How to contribute

• Has a community backlog with work to pick up?

[github-actions]

Thanks for your submission, @openedx/open-edx-project-managers will review shortly.