[Feature] Make it a bit more enterprise friendly

[GregPick]

Hi. I have a few suggestions that would make SysTrayMenu more acceptable in an enterprise environment:

1. A setting to reduce the context menu items, from this…

…to this…

2. An option to require and set a password for entering the Settings menu.

3. The ability to set a custom string for the caption when hovering over the icon in the system tray, rather than ‘SystemTrayMenu’.

Thank you!

[topeterk]

Hmm never thought about that but sounds quite interessting.

As the settings are stored for the user he would still be able to alter the files where the settings are stored. If this is fine "to lock out normal or unfamiliar users" this could be done more easily.
But a full blown solutions where settings are stored in some "corporate storage" which is write protected by some company access rights or anything similar could be more difficutly to implement.

Would you think the first/easier option would be sufficient?

Chaning the name also sounds interesting, so we might have a look at this.

[GregPick]

Hi Peter, Thank you for you reply. For our purposes, it’s sufficient just "to lock out normal or unfamiliar users" so they don’t wander into settings and screw things up. Another (possibly better) approach would be to have an option to hide the Settings menu item altogether, but then we’d need a separate Settings tool to modify the user.config file, which would be fine with us.

…

-Greg P.S.: I’ve also corresponded directly with Markus. Just FYI. From: Peter Kirmeier ***@***.***> Sent: Monday, February 3, 2025 1:12 PM To: Hofknecht/SystemTrayMenu ***@***.***> Cc: Picklesimer, Gregory ***@***.***>; Author ***@***.***> Subject: Re: [Hofknecht/SystemTrayMenu] [Feature] Make it a bit more enterprise friendly (Issue #541) Hmm never thought about that but sounds quite interessting. As the settings are stored for the user he would still be able to alter the files where the settings are stored. If this is fine "to lock out normal or unfamiliar users" this could be done more easily. But a full blown solutions where settings are stored in some "corporate storage" which is write protected by some company access rights or anything similar could be more difficutly to implement. Would you think the first/easier option would be sufficient? Chaning the name also sounds interesting, so we might have a look at this. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/Hofknecht/SystemTrayMenu/issues/541*issuecomment-2631720094__;Iw!!AbgBjg!2VlLxc0rb5ad9sacpjLbIbQKyisO8uydCSVFPP4ZZ8j_3SXJxjwYV98exH_CE2Ii0hrY9NJvcEdO3XWrRymlyTwvyLxqN0Y$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AVFBLOEGO6LSAEDWBFS23CL2N6WO5AVCNFSM6AAAAABWGMP2M2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZRG4ZDAMBZGQ__;!!AbgBjg!2VlLxc0rb5ad9sacpjLbIbQKyisO8uydCSVFPP4ZZ8j_3SXJxjwYV98exH_CE2Ii0hrY9NJvcEdO3XWrRymlyTwvQihl7pk$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

________________________________ This e-mail, including any attachments, contains confidential information of Bain & Company, Inc. ("Bain") and/or its clients. It may be read, copied and used only by the intended recipient. Any use by a person other than its intended recipient, or by the recipient but for purposes other than the intended purpose, is strictly prohibited. If you received this e-mail in error, please contact the sender and then destroy this e-mail. Opinions, conclusions and other information in this message that do not relate to the official business of Bain shall be understood to be neither given nor endorsed by Bain. Any personal information sent over e-mail to Bain will be processed in accordance with our Privacy Policy (https://www.bain.com/privacy).

[GregPick]

On second thought, we wouldn’t necessarily need a separate Settings tool. We would just need to have one computer where we haven’t hidden the Settings option. Or we go into the user.config and re-enable it there if we want to make a change. That would certainly be the easiest solution. From: Picklesimer, Gregory Sent: Tuesday, February 4, 2025 9:32 PM To: Hofknecht/SystemTrayMenu ***@***.***>; Hofknecht/SystemTrayMenu ***@***.***> Cc: Author ***@***.***> Subject: RE: [Hofknecht/SystemTrayMenu] [Feature] Make it a bit more enterprise friendly (Issue #541) Hi Peter, Thank you for you reply. For our purposes, it’s sufficient just "to lock out normal or unfamiliar users" so they don’t wander into settings and screw things up. Another (possibly better) approach would be to have an option to hide the Settings menu item altogether, but then we’d need a separate Settings tool to modify the user.config file, which would be fine with us.

…

-Greg P.S.: I’ve also corresponded directly with Markus. Just FYI. From: Peter Kirmeier ***@***.******@***.***>> Sent: Monday, February 3, 2025 1:12 PM To: Hofknecht/SystemTrayMenu ***@***.******@***.***>> Cc: Picklesimer, Gregory ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: Re: [Hofknecht/SystemTrayMenu] [Feature] Make it a bit more enterprise friendly (Issue #541) Hmm never thought about that but sounds quite interessting. As the settings are stored for the user he would still be able to alter the files where the settings are stored. If this is fine "to lock out normal or unfamiliar users" this could be done more easily. But a full blown solutions where settings are stored in some "corporate storage" which is write protected by some company access rights or anything similar could be more difficutly to implement. Would you think the first/easier option would be sufficient? Chaning the name also sounds interesting, so we might have a look at this. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/Hofknecht/SystemTrayMenu/issues/541*issuecomment-2631720094__;Iw!!AbgBjg!2VlLxc0rb5ad9sacpjLbIbQKyisO8uydCSVFPP4ZZ8j_3SXJxjwYV98exH_CE2Ii0hrY9NJvcEdO3XWrRymlyTwvyLxqN0Y$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AVFBLOEGO6LSAEDWBFS23CL2N6WO5AVCNFSM6AAAAABWGMP2M2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZRG4ZDAMBZGQ__;!!AbgBjg!2VlLxc0rb5ad9sacpjLbIbQKyisO8uydCSVFPP4ZZ8j_3SXJxjwYV98exH_CE2Ii0hrY9NJvcEdO3XWrRymlyTwvQihl7pk$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

________________________________ This e-mail, including any attachments, contains confidential information of Bain & Company, Inc. ("Bain") and/or its clients. It may be read, copied and used only by the intended recipient. Any use by a person other than its intended recipient, or by the recipient but for purposes other than the intended purpose, is strictly prohibited. If you received this e-mail in error, please contact the sender and then destroy this e-mail. Opinions, conclusions and other information in this message that do not relate to the official business of Bain shall be understood to be neither given nor endorsed by Bain. Any personal information sent over e-mail to Bain will be processed in accordance with our Privacy Policy (https://www.bain.com/privacy).