Context

When setting up a Backstage integration for a specific space in Spacelift, you might notice that some stacks from the root space are visible in the integration, even though the integration was created for a different space. This behavior can be unexpected if you're trying to limit the integration to only show stacks from a specific space.

Answer

This behavior occurs when space inheritance is enabled for your target space. Here's what you need to know:

• When inheritance is enabled for a space, stacks from the parent space (such as root) will be visible in the child space

• The Backstage integration will have read-only access to these inherited stacks

• The integration cannot trigger runs on the inherited stacks (triggering requires Writer or Admin permissions)

If you want to limit the integration to only show stacks from your specific space, you can disable inheritance for that space.

For more information, refer to:

• Space Inheritance documentation

• Permission Comparison documentation