Thank you @tschumilas,we do have the same case in France as well. We have a staging server so at the beginining we were using this one as a playgroun, but we realized that hubs were putting time to put info and then if they decide to use it for real they needed to redo everything in the production environment, so my idea on this is: I think that’s ok if all the tests are done in the real platform as long as they remain “unvisible”.
So I won’t recommend a global playground at least we didn’t find the local one practical in France 
Then I see 2 situations:
- you have created an account for a hub to demo it, or the hub has created his account during a demo workshops. If after that they don’t decide to move forward, you can delete the info in the database (@Kirsten that’s what I understood when I asked that some months/years ago) It’s a bit tricky as you need to have someone who can go into the database and deleter entries, and not really “clean” either… maybe we could have an “archive” option that would not delete but make all the info disappear from all lists, etc. (and be stored somewhere in the database as “archived”). That could be applied to users as well btw, we had an issue with a user asking to be erase from our servers, we had no option than go into the database and make a hard suppression. Would this be possible technically @maikel @RohanM
- visitors learning about OFN connect and decide to try out the interface, so they create a profil, try some stuff and never move forward. Here I would suggest more a “welcome process” management as suggested Managing new user accounts, so if you follow the different “leads”, you contact them and maybe after some time of inactivity and no anwer you can set up a process where you archive the account.
Do you see any other @tschumilas?
Probably @sstead will have inputs on that 