Yes, agreed that this should be documented better. Making it so this has to be rediscovered over and over is not the best.
I implemented this process years ago after the original concept of applying "No Access" to clear selective access (recommended by Anaplan) turned out to be too system-intensive and they asked that we didn't do that anymore. LOL.
One other tip is that if selective access security changes and you're applying new security via a model-to-model import, you'll need to clear the existing security before applying the new... selective access is amended during an import, not replaced. That caused some heartburn when we were building out our initial set of models, but at least we found out before we went live. Our QA folks really earned their pay on that project...
Feel free to go check out my HUB session from 2018 that discusses creation of a separate User Configuration model to handle user security in a centralized fashion so that it can be served out in a hub-and-spoke manner to user models. It might make your life a lot easier!
Just finished watching this video. Brilliant hidden gem - wow, I wish I saw this before I started my last project. Would have saved a lot of time. Thanks for sharing this Stacey. Simon Properties are beautiful. Wow! Hope you all came out okay with the Pandemic and all.