Configuration Inheritance

soos supports a multi level configuration inheritance system, where default configurations can be set, optionally locked, and overridden as needed organization level configurations organization level configurations, allow clients to set default configurations that will flow down to all sub org and project configurations within those sub orgs as defaults if the configurations are locked then the value will not be able to be overridden by the sub orgs or project configurations if the configuration is not locked, then the sub orgs or project configurations will be able to specify overrides for these values only applicable for customers who have purchased the organization management docid\ dplmqtdtqbzcugbpiauyg add on in the example below, the organizational level configuration has set a default set for the use lock file , scan full dependency tree , and include dev/test dependencies configurations the scan full dependency tree configuration has also been locked , ensuring that no sub organizations can change the scan full dependency tree configuration configuration locks and overrides typically apply to specific configuration values or in some cases, groups of related configurations organizational level configurations sub org level configurations sub org level configurations, allow clients to set default configurations that will flow to all projects as defaults sub org level configurations cannot be locked for customers without the organization management docid\ dplmqtdtqbzcugbpiauyg add on, sub org configurations will be the global level of configurations, which are then overridable by project configurations building on the example above, the use lock file configuration has been overridden and turned off for this sub organization this will apply by default to all projects in this sub organization, unless they have a project level override (see below) the scan full dependency tree and include dev/test dependencies are being inherited note, that the scan full dependency tree cannot be overridden any configuration which is not explicitly overridden at the sub organization level (using the override toggle), will use the global organization level configuration value sub organization configuration example project level configurations project level configurations are the most granular level of configuration available and are related to a specific project in this final example, we have selected the my app project, and have turned use lock file back on, as well as turning on include dev/test dependencies these configurations will only apply to the my app project note, that the scan full dependency tree still cannot be overridden any configuration which is not explicitly overridden at the project level, will use either the sub organization level configuration (if an override exists), or the organization level configuration project level configuration