I considered using the import and export settings in resharper to maintain consistent settings in the commands, however this was unfavorable because you had to import settings on each computer for each user account. For example, if you log in as another user on the same computer that is already configured, you need to reimport the settings.
General command settings
In the end, I selected Team Shared options that store the settings in your source repository (the file will be something like <solution name>.dotSettings . When you edit the settings in ReSharper, you will need to remember them in the Team settings.

You can also save Live files and templates in the solution. They will also be stored in the dotSettings file.

Override
This will not apply the same settings as developers can override on each user base, saving personal settings on their computer.
Stubbornly
As I mentioned, if you do not include files created by ReSharper in Source Control, the settings will not be saved in the command. Do not include <solution name>.dotsettings.user , as these are user settings and should not be included.
Several projects
If you want to have the same settings for several projects, you need to either copy the settings files and rename the file name to match the solution name, or import them. I think this works better than forcing the same settings across all teams, as it allows each team to decide how they want to work.

Bronumski
source share