This would be useful since most datasets would use many external identifiers and can be time consuming to add them to MediaWiki:Wikibase-SortedProperties along with having to add the other properties to stop external identifiers coming before other properties, could also be useful if you could add statement groups for properties other than external identifiers as it is possible in regular wikibase installs but external identifiers would probably be the most used.

$wgWBRepoSettings['statementSections'] is the setting that would need to be set for cloud wikis.

On wikidata this looks something like this:

'item' => [
			'statements' => null,
			'identifiers' => [
				'type' => 'dataType',
				'dataTypes' => [ 'external-id' ],
			],
		],
		'property' => [
			'statements' => null,
			'constraints' => [
				'type' => 'propertySet',
				'propertyIds' => [ 'P2302' ],
			],
		],
	],

It could also be an idea for this to make its way into the default wikibase settings if folks think that makes sense

In T310898#8148146, @Addshore wrote:

It could also be an idea for this to make its way into the default wikibase settings if folks think that makes sense

I think this would be most expected / wanted property order, I doubt anyone would want external ids mixed in with defining properties

If $wgWBRepoSettings['statementSections'] is set for cloud wikis, will it be possible to overrule this setting by adding a custom property ordering page such as https://kbtestwikibase.wikibase.cloud/wiki/MediaWiki:Wikibase-SortedProperties ?

In T310898#8164510, @OlafJanssen wrote:

If $wgWBRepoSettings['statementSections'] is set for cloud wikis, will it be possible to overrule this setting by adding a custom property ordering page such as https://kbtestwikibase.wikibase.cloud/wiki/MediaWiki:Wikibase-SortedProperties ?

The sorted properties page will allow sorted of properties within sections, but not the creation of alteration of sections themselves as it stands