Designing in Playbook Studio
Real-time co-editing in Studio
Two people in the same template — what teammates see while you edit, what they don't, and what to expect.
Real-Time Collaboration
Multiple people can work on the same template at the same time.
When someone makes a change—adding a session, updating a title, editing an agenda item, or publishing a new version—those changes automatically appear for everyone else viewing the template.
There is no need to refresh the page or manually reload the template.
How collaboration works
Gleo uses live synchronization to keep templates consistent across all connected users.
The goal is simple:
People see the results of each other's work in near real time. When a teammate changes the template, everyone else sees the updated structure and content automatically.
Today, collaboration focuses on synchronizing template data rather than showing detailed editing presence.
What syncs automatically
Template structure
Adding, removing, renaming, and reordering phases, sessions, and other playbook elements.
Property changes
Titles, descriptions, durations, themes, marketing content, roles, and other property panel edits.
Agenda & prep content
Activities, steps, breaks, preparation tasks, and related content updates.
Save & publish actions
Draft saves, published versions, and status changes are reflected across connected users.
What doesn't sync
Some parts of the Studio experience remain personal to each user.
No live cursor presence. You won't see where teammates are clicking, what they have selected, or which field they're currently editing.
Annotations are local. Notes created on the Annotation Layer are stored locally in your browser and are not shared with collaborators.
If you need to leave information for teammates, use shared content such as:
- Playbook descriptions
- Session guides
- Preparation tasks
- External documentation
These areas are synchronized and visible to everyone.
Concurrent editing
Most collaborative editing works exactly as you'd expect:
- Add a session and everyone sees it appear.
- Rename a phase and everyone sees the updated name.
- Update a guide or description and others see the new content.
The only area that requires coordination is when multiple people edit the same field at the same time.
There is currently no field locking. If two people edit the same property simultaneously, the most recently saved change wins.
For larger collaboration sessions, it is usually best to divide ownership by section or area of the template.
Connection reliability
Real-time synchronization runs continuously in the background while Studio is open.
In most cases, collaboration works without any special action from users. If a network interruption occurs, Gleo automatically attempts to reconnect and resynchronize.
If something appears out of date, a browser refresh is always safe and will load the latest saved version of the template.
Testing collaboration
-
1
Open the same template in two windows
Use two browsers, two tabs, or invite a teammate into the same template.
-
2
Make a structural change
Add a session, rename a phase, or modify a property.
-
3
Observe the second window
The change should appear automatically without reloading.
-
4
Test an annotation
Create a sticky note on the Annotation Layer and confirm that it does not appear for the other user.
-
5
Refresh if needed
A reload always restores the latest saved state if you suspect something has fallen out of sync.
Best practices
Divide ownership when possible. Large editing sessions work best when teammates focus on different sections of a template.
Use shared fields for communication. Session guides, descriptions, and preparation tasks are visible to collaborators; annotations are not.
Don't worry about refreshing. Most changes arrive automatically. Refresh only if something genuinely appears out of sync.
Assume the latest save wins. If multiple people edit the same field simultaneously, the most recent saved version becomes the current version.