[Geoff Bacon]

I use a collection for each group that a member of i.e. each group has at least one collection
Selecting a collection eliminates songs for other groups from the display

I use 3 letter menemonics to identify the groups e.g. U3A, PUB, MUJ
Before importing songs, I add the mnemonic to the file name e.g. "Band On The Run - U3A.pdf"
The songs are typically imported into a collection with the same name as the mnemonic (U3A fo the above song)
This allows easy identification of which group a song belongs to and also allows filtering bu mnemonic and/or collection name.
Note: When Importing select "Use Filename as Song Title" rather than "Guess..." (Guess inserts spaces)

Songs can be in more than one collection (or set list)

I use setlists to arrange songs in a particular order e.g. for a gig

I don't use Albums (but some others do)

Songs have to have a unique name in the library. As I said before, I add the 3 letter mnemonic at the end of the name e.g. "Band On The Run - U3A". This ensures song names don't clash. It also means that each group has a different song file even if the content is the same (this allows versions to diverge without affecting the other groups)

For setlists, I name these in the format "venue yyyy-mm-dd comment" e.g. "MUJ Jam 2025-05-30"
Before a gig, I add one or more spaces to the start of the name - this puts it in the # category near the top of the screen (easy to find)
After the gig, I use "3 dots" "Rename" to remove the spaces and the setlist disappears under it's sorting letter (in ascending date order); useful if you want to remember what you played at that venue previously

You could have separate libraries per group but that wasn't available when I started and probably confuses things.

My suggestion is you keep it simple and after experimenting with it, be prepared to discard it all and rebuild the library from scratch i.e. don't put a lot of effort in setting up the libraries until you are sure that is how you want to work.

Hope that helps

Geoff