This would be very helpful!

Relatedly, once the finished version is released, is it once license per user, or will a single license be able to cover an entire team?

Can understand the desire for this definitely - it's a good idea! This is likely to be a medium to long-term feature due to the need for server infrastructure and the complexity of building a settings sync like this.

Some fact finding questions/brain dump for later:

1. Would you see it as being a two-way sync? - i.e. if you make changes Lavinia gets them, or if Lavinia makes them - you get them Or one person has the authoritative version and the others subscribe to that (in which case, we'd maybe disable settings for the subscribed instances)
2. If two-way, how do you reckon we should treat the scenario where one person updates a setting at the same time as the other but to different values? Guess we could go with whoever made the change last gets to keep it.
3. Printers-wise - this one's tricky coz we'd need to be able to guarantee the same driver and driver version on both machines (this is needed for printer settings recall). I guess there could always be a little notifications drawer at the top of the screen with a notification for any failed sync attempts. You as a user then know you need to take action and resolve the driver mismatch.
4. Given the complexity, how would exporting a settings file and importing it manually into the other user's machine be? Could ease the transition to the other user by emailing the file directly to them?