Let's look at this in another way.
Maybe we should be thinking about vMix User Groups. On websites that I administrator I am the highest level User: the Super Administrator.
Then there are different subgroups which give other users certain things they can do or cannot do. For example some users can write website posts but they are not given permission to publish the posts. Only a user who is a "Publisher" can approve and decide to publish another lower level user's post. This can prevent content being published that is embarrassing to the company.
For example, as Super Administrator I can configure the website, do backups, upgrades etc. Under me I have Administrators, Editors, etc. Etc. They have limited access, based on their level of skills and other criteria.
Some users are given permission to do only one very specific thing.
Perhaps User Groups is something that should be looked into with vMix. Only a Super User, for example, could get into the main Settings.
For example, a well-meaning but not as skilled temp employee or volunteer -- with no malicious intent -- could cause issues with improper use of the web controller.
A score keeper should not be able to accidentally push the Stream button. Or Close an Input.
Just like vMix's Advanced and Basic mode, each user group, perhaps should see only specific functions in the vMix back end that their user group has permissions to access. That's how it works in most of the websites where I am the Super Administrator. Only I can see the configuration section,only I can even see the backup section, only I can see the specific menu item where I do a website upgrade.
On E-Commerce sites that I build only Owners or people with owner's permission have access to the analytics reports or the financials section. Example — the owner would give their Accountant access to the financials. Not even I as website admin can see the financials if the owner doesn’t want me to see them. Remote fulfillment services have access limited to the product categories they are authorized to ship.
Lower level users can't even see these sections on my e-commerce sites. Besides providing security, it makes the administration of the back end of the websites less daunting to the less skilled newbie users. Less buttons and panels to navigate through. Less tech phone calls and emails to me from a confused new employee.
Would having User Groups on vMix be a headache? Not really. I could make everyone an Administrator, for example.
Having vMix user groups, would give me one less worry to think about during a complicated production. And it can be reassuring to know if a mistake was made that I was the one who made it when it comes to troubleshooting an event issue.
As I think about this, I would not want a well-meaning and even a skilled user touching the vMix main settings unless I was made aware of it in advance.
There are Best Practices good reasons why websites have user groups. Perhaps now is the he time to consider if Best Practices for our more and more robust and wonderful vMix should initiate User Groups.
Attached is a graphic of the permissions system of an ecommerce platform that I work with. See how finely tuned permissions can be on that platform...
Rowby
rowby attached the following image(s):
e-commerce site persmissions.png
(37kb) downloaded 3 time(s).You cannot view/download attachments. Try to login or register.
