What can the Developer role do that others cannot?

The Developer is the top-level technical owner of the deployment. Uniquely, the Developer runs the first-run setup wizard, activates which of the six product types are available, chooses single- vs multi-vendor mode, enables or disables modules, manages the domain name and global configuration, and makes the foundational setup decisions (like the master-product toggle) that shape…

The Developer is the top-level technical owner of the deployment. Uniquely, the Developer runs the first-run setup wizard, activates which of the six product types are available, chooses single- vs multi-vendor mode, enables or disables modules, manages the domain name and global configuration, and makes the foundational setup decisions (like the master-product toggle) that shape how the whole system behaves. These are deployment-shaping powers that operational staff don't have: an Admin manages products and orders *within* the configuration, but the Developer decides *what the configuration is*. In short, the Developer sets up the machine; everyone else operates it.