Module 5 · Lecture 5.1
Beyond Q&A: Dashboards, Agents & Canvas as VKL
Transform a Canvas, agent, or dashboard into VKL so it becomes a version-controlled part of the Knowledge Graph.
A Canvas, agent, or dashboard you are proud of deserves the same guarantees as the rest of your configuration. This lecture shows how to transform such an item into VKL, so it becomes part of the Knowledge Graph itself: version-controlled, edited in Veezoo Studio, and delivered to users through the normal branch workflow.
The demo starts on a branch with a pricing what-if Canvas, transforms it, and then does the same for an agent. Along the way you see what changes about editing once an item lives in the Knowledge Graph.
Key points
- Transform to VKL makes a Canvas, agent, or dashboard part of the Knowledge Graph.
- The demo works on a branch and uses the "Transform to a VKL canvas" action.
- After the transformation, Creators edit the item in Veezoo Studio.
- Saving from the visual interface only offers to create a new Canvas and cannot replace the VKL one.
- To change a VKL Canvas outside Studio, edit it agentically so the change goes through the Knowledge Graph.
- VKL items appear in version control, including rollback to an earlier version.
- Pushing the branch brings the VKL Canvas and agent to everyone on Main.
Check your understanding
What does transforming a Canvas into a VKL Canvas do?
The transformation moves the Canvas into the Knowledge Graph, where it is version-controlled and edited in Veezoo Studio.
You edit a transformed Canvas in the regular visual interface and save. What happens?
The visual interface can create a new Canvas but never replaces the VKL one. Updates go through the Knowledge Graph.
You transformed a Canvas and an agent on your branch. How do users get them?
VKL items travel with the Knowledge Graph, so a normal push to Main delivers them.