Summary

From #8475 (comment):

Currently, KeePassXC sets the "default" alias to the currently active database tab, as long as it has a group exposed to Secret Service. This should be managed through a dedicated settings UI, along with other alias mappings.

Context

As it is, if there are two databases with exposed groups, switching between them to do something completely unrelated to Sercret Service can cause client apps to access the wrong database.

Furthermore, the spec suggests there should be an interface to manage alias mappings in general:

For applications like password managers it can be useful to allow the user to configure which collection is associated with which well known alias.

The full mapping should probably go to application settings, and either file path or UUID can be used to identify the database. Maybe both: file path for loading, UUID to make sure it's the correct database.

In addition, when the user exposes a group to Secret Service, they should be able to specify an alias for the database (or leave it blank). If there is no "default" alias defined yet, that should be preselected.

May be related to #7574 (comment) (plus the two comments above it for context).