Uploaded November 2026 | Updated November 2026, 3 days ago
In this episode of AI Coding with Dr. Chuck, I work on the administrative side of Tsugi’s LTI 1.3 support.
Dynamic Registration is already working, but the resulting tool configuration is spread across a highly relational data model: registrations, deployments, scopes, claims, placements, messages, organizations, and courses.
The goal is to turn that joined-up view into an editor.
Rather than simply deleting configuration entries, I want administrators to be able to enable and disable things such as LTI scopes and privacy claims while preserving the underlying registration data. That lets a deployment grant less access than the tool originally requested.
We build and test an editing interface for LTI 1.3 registrations and deployments, including:
• Adding and removing scopes
• Enabling and disabling scopes
• Controlling name and email claims
• Editing placement information
• Working with predefined LTI and platform-specific vocabularies
• Testing that disabled claims actually disappear from launches
• Keeping the underlying relational model intact
The interesting part is that the UI presents what looks like one editable object even though the data actually lives across several related tables.
Toward the end, I also clean up the placement vocabulary so standard LTI placements and Canvas-specific extensions are more clearly identified.
Topics include:
LTI 1.3
LTI Dynamic Registration
LTI deployments
OAuth scopes
LTI claims and privacy
LTI placements
Canvas extensions
Relational database design
CRUD interfaces
Tsugi
AI-assisted software development
In this episode of AI Coding with Dr. Chuck, I work on the administrative side of Tsugi’s LTI 1.3 support.
Dynamic Registration is already working, but the resulting tool configuration is spread across a highly relational data model: registrations, deployments, scopes, claims, placements, messages, organizations, and courses.
The goal is to turn that joined-up view into an editor.
Rather than simply deleting configuration entries, I want administrators to be able to enable and disable things such as LTI scopes and privacy claims while preserving the underlying registration data. That lets a deployment grant less access than the tool originally requested.
We build and test an editing interface for LTI 1.3 registrations and deployments, including:
• Adding and removing scopes
• Enabling and disabling scopes
• Controlling name and email claims
• Editing placement information
• Working with predefined LTI and platform-specific vocabularies
• Testing that disabled claims actually disappear from launches
• Keeping the underlying relational model intact
The interesting part is that the UI presents what looks like one editable object even though the data actually lives across several related tables.
Toward the end, I also clean up the placement vocabulary so standard LTI placements and Canvas-specific extensions are more clearly identified.
Topics include:
LTI 1.3
LTI Dynamic Registration
LTI deployments
OAuth scopes
LTI claims and privacy
LTI placements
Canvas extensions
Relational database design
CRUD interfaces
Tsugi
AI-assisted software development










