Hello @Dave Grandon
You can work externally on Bamboo to restrict the merger of changes to the master/main branch by implementing a Pull Request and approval mechanism. That way your developers will be able to push their changes to their own branches and only merge to master when a Pull request is approved and merged.
Another strategy you can adopt is to modify Bamboo in a way that the repository attached to a Plan does not have "master/main" as the default Branch. For that, you need to modify the repository settings and declare another branch as the default.
You can then modify the Plan permissions to allow developers to only run builds and not edit the Plan.
If you want to have full control over the changes to the Plan structure, you can consider migrating the plan to Bamboo Specs (configuration as code).
Best regards,
Eduardo Alvarenga
Atlassian Support APAC
--please don't forget to Accept the answer if the reply is helpful--
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.