Skip to main content

Glossary

Common terms used throughout bluefactory and this documentation.

Account — Your company's bluefactory workspace: team members, connected orgs, settings, and subscription.

Anonymization — Replacing real values with realistic random ones (names, emails, addresses…) during a restore or sandbox seeding, so that sensitive data never lands in a test environment.

Archive — The module that captures records to storage, verifies the copy, then deletes the records from Salesforce to free up space.

Auto-archive — An archive setting that runs the archive automatically on its schedule, without manual launches.

Backup — A saved configuration describing what to back up (org, objects, filters), how (full or incremental), and when (schedule).

Backup run — One execution of a backup. Each run produces a snapshot and a report.

Dedupe — Short for deduplication: finding groups of duplicate records and merging each group into a single surviving record.

Full backup — A run that captures every record in scope.

Incremental backup — A run that captures only records created or changed since the previous run. bluefactory reconstructs the complete data set automatically when you use the snapshot.

Metadata — Your org's configuration and code: objects, fields, Flows, Apex classes, layouts, profiles, permission sets, and so on.

Org — A Salesforce environment (production or sandbox) connected to bluefactory.

Owner — The user who created the bluefactory account. Owners have full access to every module and are the only users who can manage roles, team members, and destructive settings.

Prepared snapshot — A snapshot loaded into a fast query workspace so interactive tools (like the Query Console) respond instantly.

Purge — Permanent deletion of Salesforce records with no copy kept, protected by a pre-flight review.

Restore — Writing data from a snapshot (or from an archive) back into a Salesforce org.

Sandbox seeding — Filling a sandbox with a realistic subset of production data, usually anonymized, using the restore engine.

Scope — The precise definition of which objects and records an operation touches, built visually with the scope builder.

Snapshot — A point-in-time copy of data, files, and metadata produced by a backup run.

Tracker — A Metadata Change Tracker configuration for one org: it captures snapshots of the org's metadata on a schedule and records what changed between captures.

Winner rule — In Dedupe, the rule that decides which record of a duplicate group survives the merge.