📄️ Managing Team Access and Roles
mtdt.io is built for teams. Everything you connect — orgs, repositories, deployments, backups — lives in a shared team workspace, and roles control who can do what inside it.
📄️ 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.
📄️ Approval Workflows: Who Requests, Who Signs Off
As a team grows, letting everyone deploy straight to production stops being convenient and starts being risky. mtdt.io approval workflows put a second person between a proposed change and the org it lands in: one person requests a deployment, another approves it. The whole handshake lives in the shared team workspace, so there are no exported files, no shared logins, and a permanent record of who signed off on what.