Lock canvas objects

Use object locks to protect important canvas layout and reference material from accidental edits, and understand who can unlock them.

Lock canvas objects when important layout should stay in place while people work around it: background shapes, section headers, facilitator instructions, imported reference screenshots, approved diagrams, final review frames, and page structures that should not shift during a live session.

Object lock is an editing guardrail that prevents accidental movement and content changes inside an editable canvas, while protected locks also restrict who can delete an object. It is not access control. To decide who can open, view, comment on, or edit the canvas at all, use Share a canvas and workspace roles; use object lock to decide which objects stay fixed while people edit nearby content.

Object context menu with lock actions

When to lock objects

A locked object stays visible, but it cannot enter edit mode until it is explicitly unlocked. Common editing actions are unavailable while it remains locked, so editors and external collaborators can share a canvas without dragging a frame, changing its content, or moving a template background by accident. Broad actions like Select all can also skip locked objects depending on the action and state. Some actions, such as copying a link, previewing or downloading allowed content, opening a linked destination, changing the layer order, or flipping an object, can remain available depending on object type, permission, and canvas state.

Lock the infrastructure of the canvas, not every working object. Facilitators lock instructions, section labels, and background zones before a workshop and leave participant areas open; designers lock approved frames and source screenshots before stakeholder review and leave open-question areas editable; template creators lock reusable structure and leave sample content editable. Good locking is invisible; over-locking makes people think the canvas is broken.

Use an ordinary lock to keep background and reference objects in place so they do not interfere while you edit other objects. Anyone with edit access can unlock these objects, and the ordinary lock does not prevent deletion. Protected locks restrict deletion to the person who protected the object and the canvas owner.

Before you lock: choose the lock type

The lock selector has two choices. Use the product labels. Support may call them a standard lock and a protected lock.

UI choiceWhat it meansBest use
Anyone can unlockThe ordinary lock. Protected from accidental edits, but any collaborator with edit access can unlock it for a legitimate change.Workshop structure, background shapes, section labels, reference screenshots, reusable template scaffolding.
Only you can unlockThe protected lock, shown with a shield-style indicator. Only the person who protected it and the canvas owner can unlock or delete it. The object must be unlocked before anyone can edit it. Guests cannot unlock protected objects.Final review frames, approved source material, facilitator-only instructions, externally reviewed layouts.

Use Anyone can unlock for most stable layout. It prevents mistakes without blocking teammates. Use Only you can unlock sparingly, when accidental change would be costly (especially in canvases shared with external collaborators); a canvas full of protected objects feels broken to everyone else.

Object lock selector

Lock and unlock objects

Select one or more supported objects, then lock them from the Inline toolbar, the Element menu, or the keyboard:

  • The inline toolbar lock button opens the lock selector, where you choose Anyone can unlock or Only you can unlock.
  • The element menu Lock applies an ordinary lock.
  • The shortcut Alt+E applies an ordinary lock to the selection.

To unlock, select the object and use the visible lock or shield indicator, the element menu, or another available unlock action. Editors can unlock Anyone can unlock objects, make the change, and lock them again. A protected object can be unlocked only by the person who protected it or the canvas owner, and guests cannot unlock it. If anyone else tries the unlock control, ALLO keeps the object locked and shows a message explaining who can unlock it. Ask one of those people to unlock the object rather than rebuilding it beside the original.

For whole-page layout, use the Page menu: Lock all applies ordinary locks to lockable objects on the current page, and Unlock all unlocks objects on the current page that ALLO can unlock for you (protected objects you cannot unlock stay protected). The shortcut Alt+Shift+E unlocks every locked object you are allowed to unlock across the whole canvas, not just the current page, so use it carefully on large canvases.

A protected lock limits unlocking and deletion to the person who applied it or the canvas owner.

Lock selector on a selected object with the protected option chosen and a shield indicator

Work around locked objects

Locked objects show a lock indicator on or near the object; protected locks use a shield, and ALLO can name who protected an object you cannot unlock. If an object will not move, edit, format, or delete, check for the lock or shield indicator before assuming the canvas is broken.

Some objects cannot be locked when you select them. Uploading files, generated outputs, and previews still processing keep lock controls disabled until the object is ready, and some types (lines, arrows, paths, and drawing-like objects) may not show lock actions at all.

Protected locks also guard destructive actions. If you try to delete a protected object that you cannot unlock, ALLO keeps it in place and tells you that the object cannot be deleted. Deleting a page can also be blocked when that page contains a protected object you cannot remove; in that case, ALLO explains that the page cannot be deleted. Contact the person who protected the object or the canvas owner. You can also fold the page to keep it out of the active flow while you resolve ownership.

Another collaborator trying to edit a protected object is stopped and told who can unlock it.

Collaborator attempting to move a shielded object with a blocked message shown

Permissions and collaboration

Object lock does not hide content from people who can view the canvas, and it does not grant edit access to someone with only view or comment permission. The two controls work together: sharing decides whether a client, contractor, or guest can enter and with what role; object locks decide which pieces of an editable page behave like fixed reference material.

This is better than making the whole canvas view-only when the recipient still needs to comment or contribute. For a client review, set sharing permission first, then lock the approved screenshots and headers and leave the open-question notes unlocked so the page still feels alive. Canvas owners should reserve protected locks for sensitive structure when external collaborators have edit access. It prevents accidental edits without making the entire canvas read-only.

Troubleshooting

  • Lock is missing. Check edit access, object type, and processing state; pending upload or generated objects may need to finish before they can be locked.
  • Only you can unlock is unavailable or behaves differently. Check whether you are a guest, whether the canvas is writable, and whether the object supports protected locking.
  • A protected object stays locked after you try to unlock it. Only the person who protected it or the canvas owner can unlock it, and guests cannot unlock protected objects. ALLO shows a message explaining who can help.
  • Unlock all did not unlock everything. Protected objects you cannot unlock remain protected, and the result depends on whether you used the page menu or the canvas-wide shortcut.
  • An object will not delete. Only the person who protected it or the canvas owner can delete a protected object. Ask one of them to unlock or delete it.
  • A page will not delete. It may contain a protected object you cannot remove. Resolve the protected object first or fold the page.
  • Collaborators say nothing moves. Too many objects are locked. Lock the canvas infrastructure, not every working object.
Give feedback

Was this article helpful?