I do do that sometimes too, but the unfortunately part of this flow is that it will make the current level dirty and people unaware of the process on the team will end up checking out the level in version control and resaving when there are technically not changes on the persistent level or sub level. Making it possessible turns it into a stored context on the current level rather than only living inside of the level sequences’ scope. If the people using it are aware of this I think it’s not a big deal and a good workaround. Everything currently up to 5.5 is more stable as a possessible but I do know they are improving workflows for spawnables though so fingers crossed for 5.6 where we can see some of that.