We’ve run into an issue where, when a board is duplicated and includes updates in the duplication, members are no longer able to edit or delete their updates on the duplicated board. According to Monday.com, and as I understand it, we should be able to edit and/or delete our own updates regardless of whether or not the board was duplicated.
Is this correct? Have I misunderstood/has anyone else run into this?
Hello @cbrunskill Yes, your understanding is right in general. On monday.com, users can always edit or delete updates they personally wrote.
The key detail is duplication. When you duplicate a board “with updates,” those updates keep their original author. On the duplicated board, you are no longer the author of those updates, so you can’t edit or delete them unless you’re the original poster or an admin.
Also note:
Updates created by automations or integrations don’t belong to a regular user, so members can’t edit them.
Guests or limited members may have extra restrictions.
Admins can always manage updates.
Dr. Tanvi Sachar
Monday Certified Partner, Monday Wizard
Thanks, Dr. Sachar. The people attempting to edit the updates were the original posters and board members, so to me this further confirms my understanding that they should have been able to edit their updates, even on the duplicated board.
That does sound off. @cbrunskill
If the same users who originally wrote the updates are members on the duplicated board, they should still be able to edit or delete their own updates. Duplication alone shouldn’t change that.
Quick checks:
Make sure they aren’t added as guests or limited members on the new board.
Confirm there are no custom permission settings blocking update edits.
Verify the updates weren’t created by an automation or integration.
If all that checks out, it’s likely a bug. I’d send it to monday.com support with examples.
Thanks! It’s helpful to get outside confirmation that it’s probably a bug. Always nice to know I’m not missing something obvious. We did reach out to support but didn’t escalate as we found a workaround that got us around it at the time. We’ve moved past it for our immediate needs, but if/when it happens again, we’ll just log a ticket.
Hey @cbrunskill Totally makes sense, and you weren’t missing anything obvious.
Glad you found a workaround for now. If it ever comes up again, logging a ticket is definitely the right move.
And if you ever want a second set of eyes on your setup, you’re always welcome to book a session with our team. We’re happy to review things and help you tighten it up before small issues turn into bigger ones. you can book a sesion here https://calendly.com/mondaywizard/30min