Why aren’t the capabilities defined in a sideloaded line-of-business (LOB) UWP app retained after installation?

Our organization have defined the following capabilities in a custom LOB UWP application:

<uap:Capability Name="userAccountInformation"/>

<uap3:Capability Name="userNotificationListener"/>

<rescap:Capability Name="broadFileSystemAccess"/>

<DeviceCapability Name="documentsLibrary"/>

However, after installation, users still need to manually enable these permissions in Windows Settings > App Permissions for the app.

If users forget to perform this step, the corresponding capabilities—particularly access to local files—do not function as expected.

Is there any additional configuration required during development or packaging to ensure that these permissions are enabled by default after installation, without requiring users to manually enable them through the Settings interface?