📄️ Connecting to a Salesforce Environment
Before you can deploy, back up, or analyze anything, mtdt.io needs access to your Salesforce org. Connections use Salesforce's standard OAuth flow — mtdt never stores your Salesforce password.
📄️ Setting Up Version Control Connection
Version control is your source of truth — the baseline mtdt.io deploys from, compares against, and keeps current. Connecting a repository unlocks Git-based deployments, metadata-to-Git backups, and comparisons.
📄️ Connecting S3-Compatible Storage
mtdt.io stores backups in storage you own. Object storage — your own S3-compatible bucket — is where metadata backups, archives, file backups, and CSV data backups land. You connect it once under Storages, and it's available to every feature that writes backups.
📄️ Connecting a PostgreSQL Database
Some mtdt.io features store data in a relational database you own — your own PostgreSQL. Record (data) backups and email backups write their records there, where they stay queryable. You connect the database once under Storages, alongside your object-storage buckets.