Silly Question of the Day about ClientConfig

Originally MODX did not have a "sudo" user, and it was quite possible to create element and resource groups that your (or any other) Manager user did not have permission to access. This became such an annoyance that the "sudo" user setting was added to override all other permissions settings.

https://www.linux.com/learn/tutorials/306766:linux-101-introduction-to-sudo
http://modx.com/blog/2012/05/02/revolution-2.2.2-performance-fixes-plus-some-wizardry/

Thank you so much for the tips. I am just now viewing a video posted by Menno at the moment for setting up a MODx user, and giving them limited access. Then I will begin to set up ClientConfig. This new group with limited access would be the group I would set ClientConfig to allow. Am I interpreting you correctly?

Almost! You don't have to assign specific permissions to your limited user groups for them to access the ClientConfig component and to update the phone number and other settings you have set up.

If you wanted your limited user group to also be able of changing the settings that show up (e.g. add a fax setting alongside the phone one), they will need access to the "Admin" button/view in the component. To give that access, you add the user group name to the clientconfig.admin_groups system setting. But as you say you that you will be the only one establishing the settings, you don't want that.

Thanks Mark:

I'll be delving into ClientConfig today. So far so good. I've successfully created a new user with limited access (perhaps still a bit too limited), but it seems to be working as expected.

Essentially now I have 2 MODx User Groups. One is the default Administrator, and the I created another one called DHadmin, which has limited access using the "Content Editor" Access Policy that I had duplicated and renamed, and then made minor tweaks. And, I have one users addedto my new, DHadmin group.

As a super user, I would be the only person actually determining the settings that appear in ClientConfig, but the limited user should probably have the ability to change the content held within those settings.

I'm sure this will all get easier for me to understand as repeat the process. Already after a full day yesterday of permission emersion, I am feeling more comfortable, and confident.

Thanks Mark:

I'll be delving into ClientConfig today. So far so good. I've successfully created a new user with limited access (perhaps still a bit too limited), but it seems to be working as expected.

Essentially now I have 2 MODx User Groups. One is the default Administrator, and the I created another one called DHadmin, which has limited access using the "Content Editor" Access Policy that I had duplicated and renamed, and then made minor tweaks. And, I have one users added to my new, DHadmin group.

As a super user, I would be the only person actually determining the settings that appear in ClientConfig, but the limited user should probably have the ability to change the content held within those settings.

I'm sure this will all get easier for me to understand as repeat the process. Already after a full day yesterday of permission emersion, I am feeling more comfortable, and confident.