Found somewhat of the issue…
If you have the FMOD Studio project in SVN and update SVN to get the FMOD project (outside of FMOD Studio - in SVN only), you won’t be able to access SVN within FMOD Studio as it gives the error “The project’s path “#PROJECTPATH”, could not be mapped to any location in the depot/repository.”
If you access FMOD Studio in SVN fresh by using FMOD Studio toolbar: File/SourceControl/Browse for Project - it allows connection to SVN after the project is downloaded and mostly works. However… following multiple commits, updates, etc from multiple people - eventually lock issues, out of date banks, and other issues ensue.
Per FMOD Studio/Unity setup documentation, we should be able to access the project by downloading it from SVN (outside of FMOD) but this is not the case for FMOD Studio 2.0+. This was possible in 1.0+.
Another issue to mention - the documentation for implementation to Unity contradicts itself with requiring or not requiring the full development team access to the FMOD Project. Atop the documentation, it is not required. When reading further into the documentation it is mentioned that it is required for the full team to have access to the project. Possible to get some clarification on this?