Target version: 2026.43.1

Cloud

Cloud Collaboration

CueFlow Cloud shares projects within an organization for simultaneous editing and comments. Song content and show arrangements are shared, while each device chooses its active show and playback-follow setting. Before handing work to another operator, check the cloud indicator at the bottom-right for edit and asset synchronization status.

Live edits and saved restore points

Edits are shared automatically while connected. ⌘/Ctrl+S saves on this device and records a checkpoint to return to later. “Save version” lets you add a one-line summary; saving without a summary still records the checkpoint. Choosing an organization is separate from enabling cloud sync: only projects with “Enable cloud project” turned on join co-editing.

Accounts and profiles

Co-editing requires a Team / Enterprise organization. Viewers / Commenters may join as guests; Editors can also accept invitations using a free CueFlow account. The inviting organization supplies the Editor seat. Set your display name, icon, and color when joining. Later, free-account users and guests use the account or guest menu in the header; users with a cloud-enabled license use Settings → Basic settings → Cloud Collaboration.

Organizations and seats

Organization roles (Owner / Admin / Member) apply across the organization; project roles (Editor / Commenter / Viewer) apply to the invited project. Organization members and Editors use seats, deduplicated across projects in the same organization. Viewers / Commenters need no seats. Use the organization menu in the header if you belong to several organizations. See Organizations & Plans for invitations, additional seats, and billing.

Saving and syncing a project

• Enable cloud sync — Check the organization and “Enable cloud project” when creating a project. An existing project can also be saved, assigned to an organization, and enabled. Projects with cloud sync off do not join co-editing.
• ⌘/Ctrl+S and “Sync now” — With the new sync system, these record a restorable checkpoint. A successful local save does not by itself mean the cloud copy is complete; check the bottom-right status too.
• Save status — Queued, syncing, and waiting-for-assets states are distinct. A failed checkpoint offers “Retry”. Audio and image upload/download progress appears in the same panel.
• “Lock for show” limitation — This sync-dialog option applies to projects using the older sync system. New-sync projects display that it is unavailable. For a project-wide editing freeze, use Master Lock as described below.

Opening cloud projects

Choose “Open cloud project” in the header or welcome screen and select a project. The arrangement, tracks, clips, and prompter load first; audio and images download in the background. Audio that is not ready appears as dotted clips with a download label, and the bottom-right indicator shows the item count. Automatic song advance may wait for the current song’s audio. Before a show, finish downloading the required assets and check playback on each device.

• Device copy — “Saved locally” means this device has a copy. Removing it from this device leaves the cloud project intact.
• Open offline — A cached copy can be opened, but it may not be the cloud’s latest content. Check its last-saved time and offline indicator.
• Missing audio or images — Uploads and downloads run automatically. If CueFlow reports that an asset is absent from the server, a member with the original file should open the same project and complete the upload.
• Guide video — Video placement information is shared, but video files are not transferred through the cloud. Provide the required files in each device’s project Videos folder so they can relink.

Offline editing and unsynced changes

Offline mode in the bottom-right cloud menu disconnects the session so you can work on this device. With the new sync system, unsent edits are recorded locally when a recording destination is available and sent on reconnect. If edits cannot be recorded, or you only have view permission, the project is read-only. Unsynced-edit and pending indicators mean the handoff to other devices is not complete. If changes are rejected, read the notification and inspect the preserved content in History & recovery.

Live co-editing

The song/MC library and each show’s arrangement are shared. When several shows reference the same song, changes to its lyrics, audio, and song-owned cues affect every show using it. Song order and breaks belong to each show. Concurrent edits to the same field do not necessarily keep the value saved later. Displaced values can be reviewed in “History & recovery”.

• Presence — The cloud status in the bottom-right shows connected members as emoji avatars with their colors (up to four, plus a remainder count). Hover to see what each member is editing.
• Soft-lock warning — If you edit an area another member is working in, your change is held and a “⟨name⟩ is editing …” warning appears. Only continue explicitly via “Edit anyway” when needed.
• Undo history preserved — Receiving changes from other members does not clear your undo history; only operations that genuinely conflict are skipped, with a notification.
• Change history — Open Change history in the bottom-right cloud menu to review edits, undo, restore, and save activity. Projects with cloud sync turned off do not send activity.
• Sync opt-out — Next to “Link playback,” the cloud status offers a “Sync Solo/Mute & LTC state” toggle (on by default). Turn it off to keep each track’s Solo/Mute, the Click/Count on/off, and the LTC I/O settings (receive protocol, chase, LTC/MTC/Art-Net output, etc.) local to this device — so you can audition other audio during co-editing without touching the show desk. A banner at the top of the audio, Timecode, and Beat inspectors toggles the same setting. It is per-device; volume, pan, and other values keep syncing as before.

History & recovery

• Open the panel — Open a project using the new sync system, then use “History & recovery” on its row in the cloud project list. Checkpoint rows show the summary, author, time, and completion state.
• Restore a checkpoint — Choose “Restore…” on a completed row, review the change preview, and confirm with “Restore this checkpoint”. Restoration applies changes to the current project and records checkpoints before and after. Read any preview notices: if the previous checkpoint is unavailable, for example, restoration is additive only.
• Overwritten values and deleted items — Use conflict recovery to restore a value or item within its displayed retention deadline. Restoring a deleted song or MC also restores an arrangement entry when needed. Use a checkpoint for items that cannot be restored individually.
• Recovery copies on this device — Preserved changes that could not be sent appear here when available. Copies with “Restore into this project” can be previewed and restored. Some copies are preserved for reference only. Follow any instruction to restore a deleted parent item first.
• Older-sync history — The older sync system uses saved-version lists, read-only previews, and selective restore of songs, MCs, tracks, settings, and arrangement. These controls differ from the new checkpoint panel.

Comments

Comments can be anchored to a time on the timeline or to targets such as prompt blocks, audio clips, sections, MCs, and cue/shot tracks.

• Comment lane — Markers appear in the comment lane at the top of the timeline. Click for a popup with the text, replies, and status; double-click to add a comment at that time.
• Drag to retime — Markers can be dragged; the new time is saved to the cloud (by the author or an organization member with edit rights).
• Playback bubbles — When the playhead passes a marker during playback, a small bubble with the author and text shows for about five seconds.
• Comments window — A standalone window with search and filters (unresolved only / mentioning me / my comments / current selection). @mention members to notify them.
• Follows re-anchoring — Comments automatically follow setlist reorders, changes to a previous program’s length, EoS shortening, and In-Song ripple moves (Alt-drag); comments anchored to MC blocks follow the same way. Anything past the new EoS or a timecode-block boundary is pulled onto that boundary so it never points at an unreachable time.
• Deleting a program with comments — Deleting a program that has comments prompts a three-way dialog — delete the program with its comments / move the comments to another program / cancel. Choosing move lets you pick the target song, and each comment keeps its in-song relative position (anything past the target EoS collapses onto it). Comment deletes and moves apply to the cloud immediately and are not covered by Undo (⌘Z).
• Merging or splitting songs — While online, comments on the replaced songs move to the corresponding positions in the new songs. Check the count in the confirmation dialog before proceeding. This re-anchoring is not reversed by Undo. It does not run offline or carry comments across a project import.

Session chat

Open the standalone chat window from the bottom-right cloud indicator → “Chat”. Enter sends; Shift+Enter inserts a line break. You can show chat alongside join/leave and save events, or mute just the notification bubbles. Message bodies are not stored permanently in the cloud; the shared history disappears when everyone leaves. Keep durable decisions in comments, or use “Log this session on this device” (on by default) for a text log. The chat window also opens the log folder and deletes local session logs.

Permissions: roles and per-area access

Open “Cloud project settings” from the bottom-right cloud menu. It has four tabs: Overview, Members, Share & invite, and Advanced permissions. Add members or change roles, then narrow their editing permissions by area when needed. See Organizations & Plans for the distinction between organization and project roles.

Each member gets a checkbox per area. Editors default to everything editable; unchecking an area makes it view-only for that member. Trying to grant edit/operate rights to a Commenter or Viewer shows a “promote to Editor” confirmation first, and CueFlow applies the same rule when changes are saved.

Viewer / Commenter projects are read-only immediately on opening and while offline. The header explains the restriction, and Lock Mode cannot be disabled to bypass it. Ask an administrator for Editor access and reconnect if you need to edit.

Playback follow, operator control, and Master Lock

During ordinary co-editing, devices play independently. The person sending a shared playback position takes operator control; devices that should follow enable “Link playback”. Taking operator control alone does not freeze editing across the project.

To freeze editing before a show, an Owner / Admin uses “Engage Master Lock”. CueFlow saves the current content and locks project editing. This also works with the new sync system, where the frozen content is recorded as a checkpoint. It is a separate action from the sync dialog’s “Lock for show” option. Master Lock does not expire automatically.

Operator control can be taken again if its holder stops responding. Owners / Admins are offered takeover or release of an unresponsive Master Lock holder’s lock, with confirmation before forcing either action. The ordinary Lock Mode button in the header protects editing on this device.

The active show is selected per device. A device does not follow an operator who has a different show open, and the presence display explains why. Stop or pause and select the same show to follow the same position. Reopening a project starts on the main show.

Duplicating, importing, and detaching

“Duplicate” in the cloud project list creates a new cloud project in the same organization and opens it when ready. “Save As” changes the local save location but keeps the connection to the same cloud project. Use File → “Save with Assets (Detach from Cloud)...” for an independent local copy. To bring in selected songs, use the setlist menu’s “Import songs from project…” and choose a local file or cloud project. Imports between cloud projects must stay within the same organization, and the destination must be saved first. Imported songs are independent copies; comments from the source project are not imported.

Deleting a cloud project

If you have delete permission, the Overview tab in Cloud project settings offers project deletion. Confirming the project name deletes the cloud project, saved versions, comments, and unshared assets. This cannot be undone, so create an independent copy with Save with Assets first if you need a backup. This differs from removing a local copy in the project list, which affects only this device.

Billing and seat purchase

Owners / Admins buy seats or change plans from the organization-management dialog. The cloud pill in the bottom-right opens “Cloud project settings” and “Organization settings” directly. Plans, AI credits, storage, and billing are explained in full on the Organizations & Plans page.