Development System
Separate development system for teams to build and test automations without affecting production systems, with publishing workflow to production systems.
A separate dev system lets a team build assemblies and automations without development work disrupting production automations. A single dev system can publish to one or more associated production systems.
Workflow
Typically one account per integration solution lives on the dev system. Folders inside that account organize the different aspects of the solution — for example, a folder for automations that configure settings, a folder for admin-support automations, a folder for the customer-facing templates.
Publishing
Finished templates are published from the dev system to a production system's special "templates" account. See Publish template to production and The "templates" account.
From a production system's "templates" account, templates are deployed and linked to end-user accounts. The link records which accounts received which template; it doesn't auto-update them. When you deploy a template change, you have the option to push the change to the accounts already linked to that template.
Staged rollout
Most teams test a template change with a few customer accounts before rolling it out broadly. Once the change is confirmed good, deploy it to the remaining linked accounts in one step. See Deploying automations.