At my company we like to utilize the model coordination module for internal coordination purposes, but often are working in client cloud projects where no one on our company's team has admin privileges, so every time we want to use model coordination we have to email the client for access. A lot of our clients haven't used this module, so we run into a lot of confusion when just asking to create a coordination space for us to use. Most recently we reached out to the client to create a coordination space that sees 'project files', has 'clash on', and can see subfolders, which often works just fine for what we use it for(clearly stated we were requesting a space just be created for us to use, included a snip showing we couldn't use model coordination without admin creating a space and a snip showing what the space creation choices should be). It took several back and forth emails and a phone call just for the client to understand what was needed. We run into this issue on almost every project with a new client and often with repeat clients. It would be amazing if members could create model coordination spaces for their own team's and company to utilize even if we aren't in a project native to our hub. Even with the capabilities that members with no extra permissions have in a model coordination space once an admin creates one, our team can effectively mark issues for our own model(s), so I don't fully understand why the initial space creation is locked down. Being able to create model coordination spaces that admins can see, and other teams outside of the company that created the coordination space can't see without admin granted permissions for multiple company team sharing coordination spaces.
