Autosave and concurrent editing
Save indicators, locking and conflict resolution.
Autosave and concurrent editing
VELORYZ Studio · Collaboration, review and version control Audience: Studio operators, reviewers and client approvers Guide type: Practical Studio operations guide
Purpose
Autosave and concurrent editing should be treated as an end-to-end responsibility, not an isolated button. Start by defining what will change, who can approve it and how success will be checked. Save indicators, locking and conflict resolution.
This guide covers save indicators, locking and conflict resolution. Use it as an actionable practical studio operations guide: verify the current UI and any provider configuration before relying on a control in production.
Availability and responsibility
The protected CMS supports versioned drafts and publications. Real-time multi-user canvas collaboration and an invitation/role matrix should not be described as available until implemented and verified.
Before committing time or budget, confirm who operates this workflow: the visitor, the client portal user, a Studio owner, or the delivery team. A feature described in design documentation is not automatically a public account entitlement.
Before you begin
- A named reviewer, decision deadline and exact draft or commit reference
- Specific feedback tied to page, viewport or component
- A written approval record and restoration owner
- A short list of measurable success criteria specifically for autosave and concurrent editing.
- A recovery plan if the proposed change creates a regression.
Recommended procedure
- Locate the relevant area or public route. For new projects, establish the brief at /create/; for owner-only content changes, use authenticated Studio Control at /admin. Do not assume a missing feature exists.
- Define the specific work item for Autosave and concurrent editing: capture the initial state, user intent, relevant data, permissions, expected output and what must not change.
- Follow the design and operating decisions listed below. Work in a draft, staging or reviewed project handoff where available; avoid editing live customer data experimentally.
- Review the effect with real content and realistic viewport sizes. Record any exception and obtain the appropriate approval before a public change.
- After the change, verify the public outcome rather than relying on a success message alone; preserve a reference to the reviewed version.
Topic-specific operating procedure
These steps apply to Autosave and concurrent editing. The implementation must be verified against the current Studio permissions, deployed provider connections and approved project scope.
- Explain how optimistic revision checks protect against stale draft updates in another admin tab.
- If a save conflict occurs, reload and manually reconcile before retrying.
- Do not promise real-time collaborative cursor editing or unlimited autosave without a verified implementation.
- Protect queued edits when connectivity drops and provide clear feedback on unsaved data.
Evidence to retain
- The original input or situation, and a clear before/after comparison.
- The reviewed version, responsible owner and acceptance record.
- Any limitation, follow-up decision, or safely reversible workaround.
Configuration and decision points
- Capture review comments with exact URLs, screenshots and expected outcomes.
- Separate changes to draft from changes to the published version.
- Resolve conflicting feedback with one accountable project owner.
- Publish approved work and retain a recoverable history entry.
When more than one implementation is possible, prefer the simplest approach that remains accessible, maintainable and compatible with the current source. Note any cost, licensing, privacy, ownership and performance implications before approval.
Verification checklist
- Reviewers know which version they assessed and what changed.
- No private admin token is shared for review convenience.
- Approved changes are reflected in the final release and regressions are documented.
- Rollback does not erase the audit trail.
Also confirm that the result addresses the original objective: Save indicators, locking and conflict resolution.. Review the customer-visible language, error states, navigation paths and the relevant device widths. A green build or a successful save does not by itself establish a correct production outcome.
Troubleshooting and recovery
- If edits conflict, reload and reconcile against the latest draft instead of overwriting blindly.
- If a release needs to be undone, use existing owner-controlled history and restore.
- For a disputed approval, preserve the written decision and release reference.
When asking for assistance, include the exact public URL or project reference, a concise reproduction path, the expected behaviour, actual behaviour, relevant timestamps and a redacted screenshot if useful. Never include passwords, access tokens or private customer records.
Related reading
- [Collaboration overview](/docs/studio/collaboration/overview/)
- [Comments and review requests](/docs/studio/collaboration/comments/)
- [Version history](/docs/studio/collaboration/version-history/)
- [All VELORYZ documentation](/docs/)
- [Studio documentation](/docs/studio/)
- [Help Centre](/help/studio/)
- [/create/](/create/)
- [/docs/client-portal/](/docs/client-portal/)
Operational note
This article describes the Studio workflow and its acceptance criteria. Where a self-service control is not available, the action is coordinated with the Studio team rather than silently represented as automated.
