Configuration Hierarchy and Inheritance

Azure DevOps

1. Settings can be configured at the organization, project, or repository level.
   By default, organization-level settings will be inherited by the projects in the organization, and repositories will inherit the settings of the project they belong to. Overriding is done by simply editing the configuration at the relevant level and saving.

   1. Organization admins can edit the configuration of all levels: Organization, Projects, Repositories.

   2. Project admins can edit the configuration of the project and its repositories.

   3. Repository admins can edit the configuration of the repository.

2. In the organization (A) and project (B) settings, there are toggles for disabling the ability to override in the lower levels.
   

   

   1. Under the ‘General’ tab of the Organization settings (A), use the “Disable Project-level Override” toggle to prevent project admins from overriding the settings configured at the organization level.
      Organization admins will still be able to edit the project and repository settings.

      

   2. Under the ‘General’ tab of the Project settings (B), use the “Disable Repo-level Override” toggle to prevent repository admins from overriding the settings configured at the project level. Organization and Project admins will still be able to edit repository settings.
      

      

Toggling the Disable Override options on/off and clicking the Save button at the bottom () will take you to a confirmation screen, where you can discard of confirm the change:

Bitbucket Cloud

1. Settings can be configured at the workspace or repository level.
   By default, workspace settings will be inherited by the repositories in the workspace.
   Overriding is done by simply editing the configuration at the relevant level and saving.

   1. Workspace admins can edit the configuration of the workspace and its repositories.

   2. Repository admins can edit the configuration of the repository.

2. In the workspace settings, there is a toggle for disabling the ability to override in the lower level.
   Under the ‘General’ tab of the workspace settings, use the “Disable Repo-level Override” toggle to prevent repository admins from overriding the settings configured at the workspace level.
   Workspace admins will still be able to edit repository settings.