Skip to main content

Locked items not really locked

  • June 2, 2026
  • 5 replies
  • 92 views

I’ve noticed since a recent update, that sometimes locked objects are not treated as truly locked.

For instance, if I lock an item, box select an unlocked item (or items) on top of the locked item, then click on the locked item; it will select them both. If I move the unlocked object, it will also move the locked object as well. Somewhat defeating the point of having the item locked in the first place.

This has happened ever since the change on how items are selected, a slightly frustrating but separate point. If I box select a few items, and then click (but not ctrl or shift click) on another item, it keeps the boxed items selected for some weird reason. I’ve never seen this behavious anywhere else; that’s literally what crtl- and shift- select are for.

I believe these two things are connected, but not 100% sure on that.

5 replies

I’ve tested changing the locked item from “anyone can unlock” to “Only board owner or co-owner can unlock”, and my colleague who is a member but not owner or co-owner can also box select items on top, click on the locked item, and then move both.


Eca
Mironeer
Forum|alt.badge.img+5
  • Mironeer
  • June 2, 2026

Hi ​@Michael Blayney thanks for reaching out! 

I wasn't able to reproduce the behavior on my side. Since the behavior you're describing could potentially be related to an account-specific conditions or a bug, I've converted this case into a support ticket for further investigation.

 

The Support team will be able to review the affected environment more thoroughly, check relevant logs, and determine whether this is expected behavior or an issue that needs to be addressed. You should receive a response shortly.

 


This is a huge issue for me now. I don’t think it has anything to do with account permissions. I have big locked backgrounds and I move elements on top, and as the first user states, miro is now becoming unusable when the locked elements join with selected groups of objects and move with them.


Hi Kaitlyn,

The support team contacted me directly, and after a fair amount of back and forth, they managed to figure out what conditions cause the problem. Miro support is still working on the why; and I have to assume once they figure it out the next patch will correct it, but I have a potential temporary fix which I’ve implemented on my computer.

Hopefully it’s the same with you.

The multi-select thing is a result of Miro recognising a touch screen; even though the mouse is still being used, it recognised an active touch screen and changed how selecting objects works; this allows you to select objects even if they’re locked. I was able to stop the unwanted behaviour by diabling the touch screen functionality on my computer.

Press the windows key, type “device manager”, select that. Find “Human Interface Devices” and expand, find “HID compliant touch screen”, right click, disable device. As soon as I did this the unwanted behaviour disappeared and Miro is now fully usable again.

Obviously you’ll need admin rights to do this, so you may need your IT team to help you. Also, if you use your touch screen for other important things then this won’t work; apologies in advance if that’s the case. Hopefully they (Miro) figure it out soon and the patch comes out.

The other solution if it’s available to you is to use a different computer that doesn’t have a touch screen.

I know neither of these options are ideal; but it’s in Miro’s hands to fix now.


I've noticed similar behavior after the recent selection changes. A locked object should remain completely unaffected by selection and movement operations, so if it can be added to a selection and moved along with unlocked items, that seems like a bug rather than intended functionality.

The second issue you mentioned also sounds related. Traditionally, clicking a new object without holding Ctrl or Shift replaces the current selection. If the previous box-selected items remain selected after a normal click, it suggests the selection logic may have changed in a way that's affecting how locked and unlocked objects are handled.

The fact that both issues appeared around the same update makes me think they're likely connected. It would be helpful if the developers could clarify whether this is intentional behavior or a regression introduced with the new selection system.