outset VS firmware_password_manager

and Outset

That sounds good! Is this the project?

Some of my machines are shared (like a lab environment) and I use outset to run a script on every login that resets the dock to the expected state. There are conditionals in there that check to see if the app is installed before trying to place the icon on the dock, so you don't end up with the ? icon.

Another option is to have Dockmaster create a package instead of a profile and install it at each user's first login with Outset. This gives the user the flexibility to modify the dock.

If it's templates in a shared folder, just reinstall the whole thing nightly (or after each user) with MDM or use outset to reinstall it locally at login.

Anything that isn't able to be achieved via config profiles, will need to scripted (see Outset https://github.com/chilcote/outset which is super useful for this). Take a look at https://macadmins.software/tools/ 'MailToOutlook 2.0') for your default email item.

Possibly outset can be of service?

There is no equivalent on macos, but you could install your shared files somewhere like /opt/company/shared and use outset to copy them into each users home the next time they log in.

I highly recommend you look into something like https://github.com/univ-of-utah-marriott-library-apple/firmware_password_manager. It will let you start managing your firmware password through packages if you want so you can push out changes to your entire fleet and supply all known passwords and it will update to your new password easily.

I currently recommend https://github.com/univ-of-utah-marriott-library-apple/firmware_password_manager as a fallback cause you can easily rotate your passwords using patch management procedures using this and not have to worry about which password it was using.