How to create a testing environment in Sanity without affecting the live application.

Hi, everyone!
My team is new to Sanity, and are taking over the project from our previous developers. We are building new features to our app, and are copying our current dataset in order to create a testing environment for new functionality. Since they are new to Sanity, they are worried that a new dataset for testing, will ruin or disturb the current live application, that is supposed to go on as is while we build and test all new functions.
So the question is, how do we make sure that the current live app is not affected by testing and developing in the cloned dataset?

export your data from your dataset, and import it to a new dataset, nothing in the live app should change

Thank you for the reply! That is what my understanding was as well, but their concern apparently is this: "maybe you are not aware of Sanity(Desk), single piece of wrong code can crash the sanity desk. That is the main reason I don't want to touch the live project" And they want to set up a whole new, cloned, project. Is this necessary? Is this an actual possibility, that it will crash the whole project?

Well as long as you dont deploy the changes it shouldn’t matter to the editors

Okay, so what they are trying to do is basically making a test environment to build and test new functionality, and this functionality is to be used in a fully redeveloped (new) app, that is currently under testing. There will be new functionality added to the Sanity studio, that will not apply to the current live application, only to the new one. Are there any issues to be aware of here, or will it not matter to the current app, as long as nothing is actively deployed to that app?In short: Can we keep one dataset going for the live application, while having the other dataset with added functionalities to an app which is under testing?
I suppose we would need to actively change which dataset the studio is working from, every time we need to do editing in the current app?

yup the schema is completely separate from the dataset

basically your dataset is only stored json documents

Okay, superb! Thanks for helping out🙌