[itsme]

@SwissMedia: Maybe you should think about your workflow, how to work with the plenty of features MobileSheets already has.

1.) "Collections"
One collection for what you call a "profile". One database for all "profiles". Change collection to switch between profiles.
2.) separate libraries
A separate library (database) for what you call a "profile". Use "Library Settings - Switch Library" to switch between profiles.
3.) a combination of 1.) and 2.)

"Mobile sheet is not oriented for chorals and big formations, or assuming every parts of the group are responsible (Big SMILE)"
If you look around in the forum you can find examples for users of all kind of musical styles and group sizes that are more than happy with MobileSheets.
E.g. search for user "Oz Cello" in the forum. He organizes the sheet music for his string quartet on different tablets and has described his workflow clearly
https://www.zubersoft.com/mobilesheets/f...10421.html
https://www.zubersoft.com/mobilesheets/f...-9491.html
https://www.zubersoft.com/mobilesheets/f...-6413.html

@Mike: for scenarios with several libraries it would help a lot to use library name + date as backup name. Using ISO date yyyy-mm-dd as it is currently the case is perfectly fine.
MobileSheets_yyyy-mm-dd.msb as backup name for mobilesheets.db would stay unchanged.
Using uppercase/lowercase as it is in the library name would look nicer as using the all lowercase database filename .
In my example shown in this screenshot    
e.g. the backup name of MSPTest / msptest.db would default to MSPTest_2025-02-15.msb