If you want to make large experimental changes to your module/application or you want to create another version for a different client, it is a good practice to duplicate this module or the entire application first before making changes. This will also ensure that all automatically saved sessions and their stats will be saved in the new module or application and are thus siloed when downloading the session stats.
Whenever you duplicate modules or an entire application, all duplicates will be set to not published. This means that the author duplicating the module or application needs to push it from the Development environment to either Test or Live by publishing the duplicated modules. If you are duplicating a module within an application, all application collaborators will have access. If you are duplicating an entire application, the modules in the application are all not published and no collaborators are copied over.
Duplicating a module
Duplicating an Application
In the application, navigate to Settings and click on Duplicate Application. The name of the duplicated Application equals existing name (copy) and can be amended. Click the button Duplicate Application again to confirm the duplication.
