Block/Allow processes with standard user accounts

[ghost]

Hello everyone,

I tried today the new stable version and I'm so far happy with that. It works and has no real internal bugs. But what I find a bit critical is the current fact (at least for me) that the app needs now to be run with a admin user account on macOS to work completely.

I'm using macOS overall with a standard user account (to give my Mac a bit more security) on my system and it's not possible for me to block/allow processes with the standard user account type there. It notifies me only if a device (audio for example) goes inactive. It doesn't give me a notification if a device goes active and if I want to block/allow it. This was in the previous version possible (counts also btw for the installation app which needs also now a admin account to run).

I hope it's possible to give the full functionality back for standard user accounts!

With kind regards IRIS

[jab3rd]

I can't even install Oversight 2.0.0 when running a standard user account. Double-clicking the installer produces an Oversight error dialog: "ERROR: Insufficient privileges. Administrator privileges are required to monitor the camera & microphone." on macOS Big Sur 11.5.1 on an m1 MacBook.

[akatwell]

I can't even install Oversight 2.0.0 when running a standard user account. Double-clicking the installer produces an Oversight error dialog: "ERROR: Insufficient privileges. Administrator privileges are required to monitor the camera & microphone." on macOS Big Sur 11.5.1 on an m1 MacBook.

Sorry to revive this a year later, but I actually have the same issue on OverSight 2.0.1 running macOS 12.4. I cannot install on the standard user account that is the only account I use for security reasons. Tried double-clicking the installer and installing through the terminal having sudo'd into elevated privileges. I haven't tried logging in and installing from the admin account since if the app cannot ask for elevated privileges from within a standard user account it is not good to me anyway since I never run an admin account. Is there something we are missing here? I feel like surely there must be a way to install and run this software properly through a standard user account.

[akatwell]

Update: if I try to install v1.2.0, unlike v2.0.1, the installation program does ask for admin credentials and installs successfully. But the application doesn't function on the standard account - when I open it it shows me the 1.0.2 menu, but the whole application closes when I close the menu (even though I set it to headless), and regardless of whether the menu is open or not it won't detect any events.