Space

Spaces are used to group configuration based on various attributes and are the primary way to manage access to Config Units and other resources. Spaces provide the highest level of isolation inside an Organization.

Spaces also function as a way to provide configuration context. In particular, Triggers are set at the space level. For this reason it is recommended to create different Spaces for different deployment environments, so that different policies can be imposed on production and non-production environments, in different jurisdictions, and so on. For instance, you may want to disallow use of high-cost features, such as backups, in development environments, whereas those features could be required for availability in production environments.

Additionally, a Space is the primary collaborative context within ConfigHub. You will be able to share Spaces similarly to how one can share folders in a file service. You can have 1000s of people in your Organization using ConfigHub but each will only see the Spaces they have access to and they will not get overwhelmed by looking at everything going on in the org.

The first time you log in to a new Organization, a default Space has been created. This is meant to make it easy to get started. In a larger organization, it is more common to create a new Space when you want to start on a new project or collaborative projects with your co-workers.

Almost all types of entities in ConfigHub belong to a Space: Target, Worker, Units, etc. You will be able to share them with other Spaces. For example, your team can be the owner and custodian of the production Environment and production Kubernetes cluster and therefore they are owned by your team's Space. But you will be to share access to them with other Spaces.