Source relocation and handoff
Refresh Data after moves or renames. Supported native tracking attempts identifiable same-volume recovery within the original scope; otherwise use Locate folder or Locate file. Unsaved SQL is preserved, historical SQL remains unchanged, and readers add current source mappings without proving identical contents. Cross-volume, removable, NAS, and cloud-synced locations are not guaranteed to recover automatically.
For a new import with physical data, choose a dedicated container: initial data restores into main/ and Additional folders into additional//. Neither directory may already be occupied. Choose a custom folder can override the Additional base. Re-enter database passwords and reconnect sources after import.
Read time: ~6 minutes · Series: Platform Admin practice · Previous: Database connections · Next: .lantide export/import
What is a workspace
Each Workspace is an isolated environment with:
- SQL tabs and cache
- Data folder (
current_load_dir) - Projects (Plan / Report)
- Connection and MCP settings (in that workspace config)
Analysts separate project lines or data environments (e.g. "promo review" vs "daily adhoc").
Common operations
| Action | How |
|---|---|
| Create | Sidebar Workspace ＋ |
| Switch | Click another workspace or right-click Switch |
| Rename | Right-click → Rename (1–40 chars, alphanumeric _ - .) |
| Delete | Right-click unused workspace → Delete |
| Change data folder | Right-click local folder row under Data → Change data folder |
Details: USER_GUIDE §3.
What isolation means
- Switch workspace → cache clears; switch back requires rerun or Source Run
- Tab and sidebar state saved per workspace
- When a bundle belongs to the same workspace history, import explicitly offers Update existing workspace or Import as separate copy; unrelated bundles create a new workspace
Planning tip: one business domain or data environment per workspace to reduce wrong-folder mistakes.
Data folder best practices
- Point at team shared or synced folder (NAS, cloud sync) with stable paths
- After machine migration two strategies:
- Rebind: bundle without physical data—pick matching folder on new machine; paths don't auto-follow
- Extract: export with Include physical data files; import wizard unpacks to chosen dir (.lantide export/import)
- Desktop Reveal in Finder / Show in File Explorer confirms current load dir
One thing to do now
Publish naming examples: ws_prod_analytics, ws_campaign_618, with wiki mapping each workspace to data folder path.