In order to access some options, such as enabling SQL Source Control in multiple instances of SSMS, you have to access a section of the setup tab that you can only get to after you have a database linked to a version control. This kind of thing should be available without having to go through all of that.

As an example of where this comes into play, I open a local DB that I have no intention of attaching to SC and do some work. I then open another DB in another SSMS instance that I do want to deal with source control. I have to close both and open them in the correct order to even be able to get to the option to make this possible.

It is my opinion that no piece of software that is intended to make my life easier should force me to close something (completing breaking my workflow) outside of completing an update.