Hi, curious for any input - I'm looking for the ideal way to set up our dev workflow with our sandbox accounts. We're about 5 developers and have 2 sandbox accounts - we mostly work on separate components so we don't overlap too much, the way that we currently use the SB accounts is pretty arbitrary. Should we divide it between the devs? Do a prod and QA division? Thanks in advance!

I think my setup is a lot different from yours (no in-house devs, I'm the solo admin), but as someone who maintains 2 SBs, I like to have one be the "playground" and the other be a backup that goes untouched outside of periodic refreshes.

We have 2 sandboxes and have TEST - QA - PROD environments. Like Dylan, we try to use TEST as the "playground" and trying new things. QA we try to keep as close to PROD as possible.

Do a DEV, QA, and Prod. Keep QA as closely refreshed to Prod as possible.

Not that "fouled testing" has been a big problem in my experiences, it would be nice if a user could easily identify records that were being tested by another user, so as to avoid them. And of course the New Release can be used as a testing environment.

Got it, thank you everyone for you advice!