Support

There is a way to achieve something similar to what you want.

Because Joomla permissions apply to the component, not individual views, you can only use permissions to control access to the component. You need to give your administrators the Access Administration Interface and Utility privileges.

Normally, this would allow them to have too much access. However, Admin Tools offers a secondary access control feature: Main Password. You can select which views will be protected behind the Main Password. Select everything except URL Redirection. Do NOT give the password to your Administrators.

Your Administrators will log into your site's backend but the only thing they will be able to access will be the URL Redirection page. Everything else will ask them for the Main Password.

So, you get kinda what you want, with a few more steps.

You may wonder, why not add individual permissions for every feature? That's 34 permissions. Per user group. Joomla creates one POST form field for each permission for each user group. If your site has a large number of user group (about 25 would do it, as there are other permissions and we have to also remember to count all of the options and about a dozen core Joomla parameters being sent in the POST) you'd end up with an Options form that has more than 1000 POST parameters. This will trigger the security features of most hosts, blocking you from changing the component's options. This is why there are only three very broad areas in the Permissions and we have implemented the Main Password feature as an additional access control.

Ideally, Joomla should be serialising the entire form into a single JSON document and then just POST that document. This is something we are already doing in Akeeba Backup because of a similar issue we came across with some servers. This would circumvent this limitation and allow third party developers with far more complex products than Joomla's fairly straightforward core components to implement far more fine-grained controls. To be clear, that's the ideal situation. I do not see anything which even remotely points to the Joomla maintainers even planning to do something like this. You can always submit a GitHub discussion or issue and point to this public ticket, but I wouldn't count on it going very far – at least not very fast. It would require some fairly deep changes to how Joomla's com_config works with some associated changes in the core MVC controller and model code to handle this kind of use case. Not impossible, but certainly not something that could be conceivably delivered outside a new major release.