Skip to content
On this page

Deleting & Undoing

"Delete" can mean retiring a board, removing a canvas element or erasing an organization, and each has different consequences.

Deletes fall into two categories: container lifecycle for boards, workspaces and organizations, and change control for board edits.

What each delete does

You did thisCategoryWhat happenedHow to undo
Disable on a boardLifecycleThe board is retired, not goneRestore it via the Disabled Boards filter
Delete permanently on a boardLifecycleThe board and every layer under it are goneYou cannot
Disable on a workspaceLifecycleThe workspace and its whole board tree are retiredEnable it again
Requested org erasureLifecycleAccess froze and a 30-day grace window openedCancel inside the window
Deleted a node or edge on a board you author freelyChange controlAn uncommitted change in your working copyDiscard
Deleted a node or edge on a governed boardChange controlA staged deletion mark — the element is still there, badgedDiscard
DiscardChange controlYour working copy revertedNothing to undo — the board is back where it was
CommitChange controlYour changes persisted; governed edits created work itemsYou do not un-commit — edit forward, like git

Retiring Containers

Boards

Disable is the default delete. The board leaves listings but stays intact. To restore it, find it with the Disabled Boards filter and use the same ⋯ menu.

If a board is still published on the web, you can't disable it. Unpublish it first, then disable it.

Delete permanently removes the board and every layer beneath it. The confirmation lists the affected boards and published surfaces, and the delete unpublishes any published layer beneath the board. There is no undo.

Note

The Root Board can't be disabled or deleted, so it offers neither action.

Workspaces

Workspaces have the same two actions. Disabling retires the workspace and its entire board tree, and enabling brings it all back. Permanent delete runs the same cascade and removes everything the workspace held.

Your organization

Organization erasure is the GDPR right-to-be-forgotten process. When you request it, access freezes immediately and a 30-day grace window opens, during which you can cancel. When the window closes, we purge everything the organization owns: workspaces, boards, sources and settings.

One state machine, three sizes: board, workspace, organization.

Changing What Is On A Board

Your first edit opens a working copy

Your first change to a board starts a working copy. Position changes, renames, new elements and deletes collect there until you commit or discard them.

The indicator is your git status

Right after an edit, the top bar counts your unsaved changes beside Save. Save the board, and the count becomes the Uncommitted changes indicator. Click it to review the changes, then commit or discard them.

Deleting here is not deleting

On a governed board, such as an app board bound to its repo, the elements mirror what the governing source says. Removing one is a claim that it should go. The element stays on the canvas with a staged-deletion badge: discard removes the mark, and commit turns it into work.

On a board you author freely, a delete is an uncommitted change like any other. Discard undoes it, and commit saves it.

Discard is git restore

Discard reverts every uncommitted change and staged deletion mark. The board returns to its last committed state.

Commit is commit + PR in one motion

Commit saves your changes. On governed boards, it also creates a work item for each app board you touched, recording what changed and anchored to the elements involved. Deleting a work item later does not undo the commit; the board keeps the change. Work items continues the workflow from there.

The one rule

Use Discard to undo edits, and Restore (Enable for a workspace) to undo a disable. Nothing undoes a permanent delete.