Appearance
Vaults
Vaults are the top-level containers for organizing files in BluePLM. Think of them as separate file repositories within your organization.
What is a Vault?
A vault is:
- A named collection of files and folders
- Stored in Supabase storage
- Synced to a local folder on each user's machine
- Access-controlled per user
Common Vault Structures
Organizations typically create vaults for:
- Product lines - "BlueROV2", "Navigator"
- Departments - "Engineering", "Manufacturing"
- Clients - "Acme Corp", "Widget Inc"
- File types - "CAD Files", "Documentation"
Managing Vaults
Creating Vaults (Admin)
- Go to Settings → Vaults
- Click Create Vault
- Enter:
- Name - Display name
- Description (optional)
- Click Create
The first vault is automatically marked as default.
Vault Properties
- Name - Displayed in the UI
- Slug - URL-safe identifier (auto-generated)
- Description - Optional notes
- Default - Star icon indicates the default vault
Renaming/Deleting Vaults
In Settings → Vaults:
- Click the pencil icon to rename
- Click the trash icon to delete (requires confirmation)
Deleting Vaults
Deleting a vault removes all its files from the server. This cannot be undone.
Vault Access
How Access Works
- Admins see all vaults automatically
- Non-admins only see vaults they're granted access to
Granting Access (Admin)
- Go to Settings → Members & Teams
- Find the user
- Click to edit their vault access
- Check the vaults they should access
- Save
Access Enforcement
When vault access is revoked:
- User is disconnected from that vault
- Local files remain but won't sync
Local Storage
Each vault syncs to a local folder:
| Platform | Path |
|---|---|
| Windows | C:\BluePLM\vault-slug |
| macOS | ~/Documents/BluePLM/vault-slug |
| Linux | ~/BluePLM/vault-slug |
Connecting to Vaults
From Welcome Screen
After signing in, available vaults appear. Click Connect to:
- Create the local folder
- Start syncing files
From Explorer
Already connected vaults show in the sidebar. Click to expand and browse.
Disconnecting
Right-click a vault in Explorer → Disconnect
This removes the vault from the sidebar but keeps local files.
Copying and Moving Files Between Vaults
With two or more vaults connected on this computer, right-click files or folders and choose Copy to Vault or Move to Vault, then pick the destination vault. Each has two lists:
- Choose location in – you pick the destination folder in the next step (the vault root by default).
- Keep folder path in – the folders the items sit in come along, placed under the destination folder.
A dialog shows what will happen before anything is written: how many files go, how many are left out and why, and what is not carried over.
What is carried: the file's content, item number, description, revision and custom properties, and its version history. References between files are recreated when both ends are transferred. Files that exist only on the server are not downloaded first; the destination lists them as cloud files.
What is not carried: workflow state, reviews and ECO tags. Transferred files start as new files in the destination.
What is never replaced: a path that already exists in the destination, on the server or on its disk, is skipped and reported. Nothing is overwritten or renamed.
Left out: files that are outdated (get latest first), ignored, deleted on the server, or have a pending move. Move to Vault also leaves out files with unchecked-in changes and files that are checked out.
Move to Vault copies first, checks the copy, and only then removes the original: the local file goes to the Recycle Bin and the server copy to the vault trash. A file that cannot be removed stays in the source vault, so a problem leaves a duplicate rather than a loss.
You need access to both vaults, and permission to create files (Copy) or to create and delete files (Move). Two vaults whose local folders overlap cannot be used together.