Posting this as a relatively minor bug that took me down until I found a workaround. Our group just uploaded a project previously managed in Perforce to Collaborate. The resulting EditorSettings.asset still had... "m_ExternalVersionControlSupport: Perforce" instead of... "m_ExternalVersionControlSupport: Hidden Meta Files" Collaborate greyed out this setting blocking the ability to remove "Perforce" directly in Editor. After initial download of a fresh copy of the project from the cloud Collaborate seemed to allow normal editing. On exiting and relaunching the Editor the console began to show perforce connection errors. Additionally Collaborate operations like file/folder delete were not allowed citing that we were "not connected". The workaround was to manually edit EditorSettings.asset file changing "Perforce" to "Hidden Meta Files". Collaborate should either make this change automatically or block the connection to Perforce on Editor load.