🌐 LTI 1.3 setup: integration with support
No more Content Builder. Now in Studio:
🚀 Intakes
❓ FAQ
🚶♀️ Walkthroughs
🌐 LTI 1.3 setup
We now support LTI 1.3 connections, making it possible to connect the platform with external learning tools using modern, secure authentication standards.
Admins can view all essential LTI 1.3 authentication details (like client ID, deployment ID, keyset URL, etc.) directly from the LTI 1.3 content integrations page before setting up a remote connection.
Why it matters?
Setting up an LTI connection requires syncing details between two systems:
The platform (course consumer).
The tool (our product, acting as course provider).
This release makes that process smoother and faster by removing blind spots and reducing support friction, providing also:
Authentication info is visible upfront, no need to create a connection first.
Info box is now shown at the top of the form for better visibility. No scrolling, no confusion.
Available when viewing an existing integration and when setting up a new one.
Who benefits?
🧠L&D and platform admins setting up new integrations
🛠 Developers or IT supporting LTI configurations
⏱ Anyone who values a faster, clearer setup process
How to access it?
Go to Control > Content > Integrations > Create LTI 1.3 tools. A window will open with all the information required to set up the connection.
First, when you click on "Create LTI 1.3 tool", a window will open and you’ll see a form to set up LTI 1.3.
Once you select or save an integration, all the required connection info instantly appear in a clear info panel that you can easily copy.
🚀Intakes now available in Studio
We’re continuing our migration from Content Builder to Studio and this time, Intakes have officially joined the party.
What’s new?
You can now create, edit, publish, unpublish, and manage Intakes directly in Studio. No need to switch to Content Builder anymore. Just head to the Guidance > Create content page and select “Intake” to get started.
🔄 Already have Intakes in Content Builder?
You can still edit existing ones there, but don't create new ones!
Why this matters?
✅ More intuitive editing interface
🌍 Built-in support for translations
📦 Reusable content across platforms
⚡️ Faster publishing and updates
🧹 One step closer to saying goodbye to Content Builder
But there is more, we’ve completed another important step:
❓FAQs can be managed entirely within Studio!
What’s new for FAQs?
✏️ Fully editable in Control navigating to Content>Guidance
🔁 Copy across platforms
🌍 Translate and localise content easily
✅ Publish/unpublish workflows
Why it matters:
Less context switching. Fewer tools to maintain. Better governance.
Last but definitely not least…
🚶♀️Walkthroughs created in Content Builder now auto-convert to Studio when opened.
One click, and it’s ready to edit in the new flow. And if you want to create new ones?
Just access the Guidance page in Control and start creating!
What’s improved:
🧭 Easy to edit, publish and copy. Everything managed int the Guidance page.
⚙️ The system handles the migration quietly in the background
✅ Once opened, they behave like any other Studio-native walkthrough
🎯 No more toggling tools, CB is effectively retired for walkthroughs too
Why this rocks:
It simplifies cleanup and makes content easilyusable again, without having to manually migrate or recreate anything. Just open it, edit it, publish it. That’s it.
