Hello there @yarhuoy,

As of today, it is not possible to disconnect a board from another board (connection made by the connect-boards column) via API.

Let me know if you have any questions!

Cheers,

Matias

Hi @Matias.Monday , noted with thanks!

Any movement on this? My Monday system design project just slammed into the huge obstacle of having no way to disconnect boards via API or via native automation… (?!)

This wouldn’t be such a big problem if the Connect Boards permissions weren’t as wonky as they are—the fact that the entire column and all of its mirror columns just become fully invisible to any users who don’t have access to even one connected board among many is counterintuitive and counterproductive.

Compound this with the flabbergasting lack of a native automatic board backup feature, even on Enterprise plans (and thus, the need for users to BUILD their own board backup processes) and you have an untenable situation.

Board A is connected to Board B, bidirectionally.

Board A is backed up (duplicated, renamed, and moved) nightly.

Users working in Board B must be able to see and interact with the Board A mirror columns that exist in Board B. But every time a new Board A backup is created, the Connect Boards column and all of its mirror columns effectively vanish from Board B.

I’ve found that neither programmatically unlinking every linked item, nor even fully deleting the bidirectional link column from the duplicated board actually disconnects it from Board B!

Advice welcome. (And no, third party apps are not on the table.)