Multiple Operators and "User"

Smarter people may correct me but I don't think there are any user-specific features inherent in Eos family software. The User function is designed to provide independent command lines and displays to multiple network consoles, not to save settings.

That said, you could probably institute a numbering convention for snapshots that, as long as every user respects them, would give them some ability to store their preferred layouts. Snapshots are stored within a showfile, and not in a user directory, so some effort would be required to preserve changes across all showfiles.

Not sure what settings you wish to save. But you can merge {system settings} to any show file which has some functionality that some users might use differently, but they do tend to be pretty show specific. As mentioned Skatr Snapshots are a way to save screen layouts as well, they too can be merged. I would avoid limiting a programmer from updating or recording specific targets, like snapshots.

When I a get to a venue to program i spend the first few minutes reviewing the settings to make sure the are set to the way my brain works. ( which it appears is generally 180 degrees out from most!) I also carry a blank show with preferences and custom Macros that i use and merge them to the show i am working on.

If the programmer doesn't change for the entire event, Maybe have each user save a base file with their preferred settings and merge in patch, pallets, excreta at the start of each event.