Skip to main content
Teamspaces, folders, and dashboards can be deleted by any workspace user with the right role. Adriel shows a confirmation modal before every deletion, so nothing gets removed by an accidental click. That means the first step in every recovery is identifying who deleted it and when.

Was it actually deleted?

Before assuming a teamspace was deleted, confirm the current user still has access to it. A teamspace that’s restricted to specific members disappears from the sidebar for anyone not on the allowlist — the teamspace still exists and other members can see it. → See Teamspace settings.

If it was deleted

Adriel logs deletions with the user, timestamp, and workspace. Support can identify which user deleted a teamspace and roughly when. In most cases the deletion was intentional — a team member cleaning up their own space — and confirming that resolves the question.Email support@adriel.com with the teamspace name, the workspace name, and roughly when it disappeared.
Ops can manually restore a deleted teamspace, its folders, views, and text widgets. This is not a supported flow — it’s a best-effort, one-time restoration from database backups. Widgets that read from live data sources come back with their configuration; the data itself is re-fetched from the sources on load.Expect a turnaround measured in days, not hours. If the teamspace is critical to daily operations, work off a rebuild in parallel rather than blocking on the restoration.
Deleting a data source is a hard delete — there is no self-serve recovery. Ops can restore a data source from a database backup as an exception, but the same “best-effort, one-time” caveat applies. Cached historical data for the data source is lost; only the connection configuration returns. Once reconnected, the source starts pulling fresh data from that date forward.
A specific version of this: a LinkedIn Organic data source that was deleted and recreated instead of reconnected in place. The recreation reset the entire cached history — Delta metrics only exist from the new connection date onward, so widgets set to earlier ranges show nothing. Support can restore the previous cache as an exception, but the safer path is to reconnect the existing data source rather than delete and recreate it.

Prevent it from happening again

  • Teamspace deletion permission can be restricted by role. Review who has permission to delete teamspaces in the workspace.
  • Warn team members before workspace cleanups that dashboard deletion is a hard delete with no undo button.
  • For critical dashboards, use the Duplicate action to keep a working copy elsewhere in the workspace before large reorgs.
→ See Managing members and access.

Still stuck?

Contact support

Email support@adriel.com with the workspace name, the teamspace name, and roughly when it was deleted. Support will identify the deleting user and confirm whether restoration is possible.