Glossary
The words used across the METAFILES documentation, in plain language.
The words you will meet in these pages, grouped by topic.
The product and the people
| Term | Meaning |
|---|---|
| METAFILES | The product: the portals, the desktop and mobile clients, Office and Talk. Shown as "METAFILES by V-Connect". |
| V-Connect | The provider of METAFILES. |
| MSP | Managed service provider: the company that runs a METAFILES site and its customer organisations. |
| Organisation | One customer of the MSP. Each organisation has its own portal, users, database, encryption key and storage. Sometimes also called a tenant. |
| Organisation ID | The short name of an organisation: 2 to 16 lowercase letters and digits, starting with a letter. It becomes the portal address. |
| Portal | An organisation's METAFILES web app, at https://<organisation>.dmsvault.cloud. |
| Organisation admin | A customer's own administrator. Organisation admins have full administration rights in their portal. |
| First admin | The administrator account made automatically for every new organisation. Its name is the organisation ID followed by -admin. |
| End user | Anyone who signs in to a portal to work with files. |
The MSP console
| Term | Meaning |
|---|---|
| MSP console | The MSP's web app for creating and controlling organisations and watching the site. |
| Operator | A named person signed in to the MSP console. Every action is recorded with the operator's name. |
| Build checklist | The 12 steps the site runs to create a new organisation, shown live in the console. |
| Retry | Runs a failed build again, continuing after the steps that already finished. |
| Tier (T1, T2, T3) | How a change takes effect: T1 at once; T2 after an undo window; T3 only as a separate, approved step outside the normal console flow. |
| Undo window | The delay before a T2 change takes effect. Any operator can cancel the change during it. |
| Cluster Policy | The site-wide defaults every organisation inherits. They can only be tightened there. |
| Reset & show | Makes a new password for a user and shows it once. The console never shows an existing password. |
| Site & Fleet | The console area that shows the site's machines and services and lets operators ask for machine actions. |
| Spare machine | A machine added to the site and held in reserve for later use. |
Files and protection
| Term | Meaning |
|---|---|
| Seats | How many user accounts an organisation may have. Disabled users count. |
| Quota | How much data an organisation may store, in GB. At the limit uploads stop; reading and deleting always work. |
| Logical data | The total size of files as users see them. |
| Physical stored | What the engine actually stores after deduplication and compression, plus versions and metadata. |
| Deduplication (dedup) | Storing identical pieces of data only once. |
| Version | An earlier state of a file, kept so it can be brought back. |
| Trash | Where deleted files wait before they are removed for good. |
| Restore point | A snapshot of an organisation's whole workspace that the engine keeps. |
| Retention | How long versions, deleted files and restore points are kept. |
| WORM | Write once, read many: files that cannot be changed or deleted while they are retained. |
| WORM-capable | An organisation created with its own locked storage so that WORM and legal hold can be used. Chosen at creation; it cannot be changed later. |
| Legal hold | A hold that stops data from being deleted, for example during an investigation. |
| Ransomware protection | A trip in the engine that stops a sudden mass change of files, holds the changes back and lets the MSP release them. |
| Device approval | A setting that makes each new desktop or mobile client wait until an admin approves it. |
| Audit trail | The tamper-evident record of every action for an organisation. Each record is chained to the one before, so a removed or changed record shows up. |
Sign-in and security
| Term | Meaning |
|---|---|
| Two-factor (2FA) | A second proof of identity, such as a code from an app, on top of the password. |
| App password | A separate password made in the portal for one desktop or mobile client, used when two-factor is on. |
| Encryption key per organisation | Each organisation's files are encrypted with its own key, so a copy of the storage alone does not reveal them. |
| Isolation check | The automatic test at the end of every organisation build that shows it cannot reach other organisations. |
| Suspended | An organisation that has been switched off by the MSP. Its portal shows "This service is suspended"; its files stay intact. |
| Read-only | An organisation whose users can still view and download, but not change anything. |
The platform
| Term | Meaning |
|---|---|
| The engine | DMSVault's own Rust storage engine. It deduplicates, versions, encrypts and protects every file, and is the core of the product. |
| S3 gateway | The engine's front door. Every file the portal stores passes through it, which is where quotas, WORM and ransomware protection are enforced. |
| Ceph | The storage cluster behind the engine on the site's own storage. It keeps three copies of everything on three storage servers. |
| Storage target | Where an organisation's encrypted data is kept: the site's storage, Amazon S3, another S3-compatible service, or the customer's own server. |
| Site | One complete METAFILES installation: its servers, network, storage and control plane. |
| Control plane | The separate system that builds organisations, carries out approved machine actions and watches the site. Users do not depend on it while they work. |
| Office | Document editing in the browser, powered by Collabora Online. |
| Talk | Chat, audio and video calls in the portal. |
| TURN relay | A server that relays call audio and video when two people cannot connect directly. |
| METAFILES Drive | The streaming cloud drive in the Windows client: files appear as a drive and download only when opened. See Cloud drive. |