Forum Discussion
Site Collection Admin in Modern Team Sites
I agree with the sentiment, which is why all of our modern UX guides users down safe paths. But as you can see from this thread, we also have a community of people who depend on being able to do some advanced, custom configuration, and don't want to leave them in the lurch. We believe that we've struck a good balance here, where unlike the past 10 years we avoid users accidentally stumbling into trouble, but empowering the experts who to get their job done. I hear your feedback that you think we need to go further, but I know if we completely block it we'll have a lot of feedback saying we went too far.
As an IT professional, I obviously want to have a complete freedom to do EVERY advanced configuration that I feel necessary for my customers (at my risk, naturally...).
Hence, IMO, you have ALREADY gone too far with blocking/hiding advanced configuration interfaces.
Nevertheless, I understand your effort to guide inexperienced users users down safe paths.
I only hope that this strategy will not impair us, experienced professionals, in our work.
In short: go ahead with hiding, if you have to, but please document thoroughly all advanced configuration interfaces and all dependencies that are in place.
Something like Simple vs Advanced mode. Simple gives you all the locked down/protect the user options, and Advanced gives experienced professional full access to go in and do what we need to do.