https://help.octopus.com/t/feature-request-variable-sets-spanning-spaces/26948/4

We have multiple teams and have so far been avoiding spaces because we have no way that we know of to share variables and scripts between teams in different spaces.

We have a lot of shared configuration that we wants accessible by all and with only one source of truth. For example, we have many apps that need to add whitelisting for our build/deploy servers. We store that ip whitelist in an octo variable set so all project can access it. If I need to alter that whitelist I can be confident that if I change the values in the variable set then the apps have the updated whitelist on the next deploy.

This doesn’t work if teams are in different spaces. I would effectively have to manage several whitelist variable sets across every space which kind of defeats the point. The reason for needing to move to different spaces for each team is that accounts (e.g. Azure Service Principles) cannot be restricted except across spaces and we want to de risk the possibility of one team using another teams account