Table of Contents

Search

  1. Preface
  2. Introducing Administrator
  3. Organizations
  4. Licenses
  5. Ecosystem single sign-on
  6. SAML single sign-on
  7. Source control and service upgrade settings
  8. Users and user groups
  9. User roles
  10. Permissions
  11. Runtime environments
  12. Serverless runtime environments
  13. Secure Agent services
  14. Secure Agent installation
  15. Schedules
  16. Bundle management
  17. Event monitoring
  18. File transfer
  19. Troubleshooting

Administrator

Administrator

Source control configuration for sub-organizations

Source control configuration for sub-organizations

Configure source control for a sub-organization on the
Settings
page in the sub-organization. As a best practice, each sub-organization should use its own source control repository. Additionally, the source control repository for a sub-organization should be different than the source control repository for the parent organization.
Maintain different source control repositories so that users in one organization do not accidentally overwrite or change assets in another organization.
If you want the parent organization administrator to be able to perform source control operations in the sub-organization, configure the Git user account for the parent organization administrator to have access to the sub-organization's source control repository.


Updated August 03, 2020