Working with Shared Deployment Projects

In mtdt.io, deployment work lives in a shared team workspace rather than on one person's machine. Connected orgs, repositories, deployments, backups, and saved selections are visible to teammates according to their role, so releases stay a team activity.

Shared by default

When you connect an org or repo, or create a deployment, it belongs to the team, not just to you. That means:

• A teammate can pick up a deployment you prepared, review it, and run it (subject to their permissions).
• Deployment history, backups, and comparison results are visible to the whole team, so there's a single shared record of what happened.
• Approvals route to the right people without anyone exporting files or sharing credentials.

A typical team flow

1. A developer prepares a deployment and validates it.
2. They request approval.
3. A release manager reviews the diff and approves.
4. The deployment runs to the target, and the result is recorded in the shared history for everyone.

Best practices

• Use approvals to hand off between preparer and approver rather than sharing accounts.
• Lean on the shared history as your team's single source of truth for what was deployed, when, and by whom.