Skip to main content

Projects and Environment Chains

A project is an ordered chain of Salesforce environments that work moves through — for example DEV → UAT → PROD. The chain is what makes promotion possible: it tells mtdt.io which environment comes next.

In a team workspace, projects live in Team Settings → Projects. A personal workspace has no Team Settings: manage its projects on the Work Items page, with Manage projects next to the project selector.

What a project holds​

  • A name and an optional description.
  • An ordered list of environments. Each environment has a name of your choosing and points at one connected Salesforce org.

Order is what matters. The first environment is where work starts; the last one is what "production" means for this project, whatever the org is called. Reorder environments with the arrows on each row.

An org can appear in more than one project. Within one project, give each environment its own org: if the next environment points at the same org as the current one, promotion refuses — there is nowhere to move the work to.

Notifications per environment​

Each environment can announce arrivals:

  • Notify team — an in-app message and an email the first time a work item reaches this environment.

Who can edit​

Every member sees the Projects tab and the chains on it. Only team admins can create, edit, reorder or delete projects. A member gets a read-only list rather than a refusal after the fact.

Permission to edit deployments does not grant permission to edit projects.

Plan limits​

A personal workspace on the Free plan has exactly one project; creating a second one is refused. A paid plan lifts the cap, and team workspaces are not capped.

Deleting a project​

Deleting a project removes its work items from mtdt.io along with it, archived ones included, and they cannot be brought back. The delete dialog shows how many work items will disappear before you confirm.

How projects are used​

  • The Work Items board draws one column per environment, in chain order.
  • Promotion derives its target from the chain — the next environment after the one the item has reached — and refuses past the end of it.

A new personal workspace gets a project called Personal on registration. Team workspaces start with none; a team admin creates the first one, and every work item needs one.