Spaces can be shared to the web (set as Public), it means they will be accessible by anyone and indexed (or not) by Google.
How to share space
Admin or Creator can Share space to the web. This space becomes available to anyone . For example, If I have xxx.fibery.io Workspace and make User Guide space Public, then ANY anon visitor will see this Space in left menu when open xxx.fibery.io. Direct link to the space will be . | Fibery
Under the hood we use read-only users mechanism, but multiplex a single read-only user for all anons visitors.
When a visitor clicks Space, she is redirected to the first View in the space
Anon visitor is read-only, she can only browse things and do nothing more.
Published space works as you have a read-only users that has access to this space only. It means the user will not have access to entities/views from other spaces, even if they are mentioned somewhere.
If you shared several spaces, all of them will be visible to anon user in the left menu.
Not sure if this is the best place to discuss, but it seems like you have evolved your product development data model to account for Releases and Roadmap Items. I was trying to account for similar concepts in our model, but it felt like it was getting convoluted with all the concepts. I’m curious how you have handled these models to help with communicating externally, including if you have implemented any automation to help.