Hey Speckleland
Are they are workspace case studies in existence, it would be cool to see how others are taking advantage of this offer.
I’m particularly interested in the granular level access, does this mean at the model level?
Cheers
C
Hey @ChrisT!
@mirna is actually working on one and we will publish it very soon.
Currently there are no model level permissions, but it’s on our roadmap. We have also heard folks wanting to create teams/groups to be able to more granularly grant permissions inside the Workspace.
Could you share what would be your ideal set up? @benjavo our product lead would love to hear!
You can also sign up for a Trial and see all the existing security settings, in short this is how it works:
- all Workspace members by default can see all projects. You can change the default, and also set custom visiblity/access to each project.
- you can also add guests to the Workspace and they will be able to access (read or write) only yhe projects they are invited to.
1 Like
Hey @teocomi, thanks for the info, good to hear on the case study!
I’m kind of struggling to see the main detailed difference between using a workspace and not. Perhaps the case study will highlight this. looking for to watching it.
My conundrum:
At the moment, in the non workspace environment, I can invite collaborators as a Contributor or a Reviewer and I can have that secured behind the private access. (which I understand to be pretty good by itself). If I want, (and I do) I can make the link sharable and share with non collaborators at a model level (which is a really interesting option for hyper focusing on areas and sharing packages (think DfMA stuff- CLT/Steel/Glulam etc) BUT it’s not ideal to have the link open to the net, so private seems like the way, however then there is no model level access. We are also making our lives a little harder here by using a local server 
Good to hear that it is on the roadmap btw, I think it will be a valuable addition.
Hey Chris,
Valid points! The main advantage of using Workpsaces is that it applies the same permissions to all projects inside the workspace, so as a team/company you don’t have to set them for each new Project.
As a workspace Admin you also get to have an overview of all users and projects part of the workspace. Finally, using the Pro and Business plan you can further secure your workspace by enabling SSO and a Custom Data Region.
Now, since you’re self hosting these features are already available in a way or another at a server level, althought you will still have to manage permissions project by project.
If you’d like to explore hosted options don’t hesitate to send me a DM, we believe our SaaS plans are a much better bang for the back than self hosting in the long run, not to mention the performance feature availability 
We are working with partners also to show how Speckle Automate is being used by organisations to streamline/augement/enhance particular workflows. This will also come soon.
Private functions for Speckle Automate are exclusive to Workspace projects.
It may not fit your interest right now, but may add to the things we can do better to demonstrate things for you…?