Hello @jai.jain , it is challenging when you have only one environment.

You can try by having different data pools (if you also decide to have dev qas prd data) and space (each space for each stage). There is no sub space in Celonis, so you have to think where or how do you want to manage the value stream etc.

Reference (studio) https://docs.celonis.com/en/deploying-studio-packages-in-a-dev-qa-production-setup.html

Hi @jai.jain,

If you want to do acceptance on a code level, you could incorporate the use of GIT repositories. Using PyCelonis, you can extract all Celonis Code in the back-end and commit it into a new release. Once accepted, you can publish this release automatically again using PyCelonis towards a section in your Celonis Environment where nobody (except of Admins) has edit rights to.

This approach is discussed here: Version control best practice (celopeers.com)

Kind regards,

Jan-peter