Mark G38

Edited because I'm silly and posted my old version.  Please see the updated and correct one below.  

There are a couple of things you can do here. 
1.  Don't give regular users Admin rights on a machine.  Of course this may not be a viable option for many businesses/end users. 
2. Delete the reg key associated with the program displaying in Add/Remove Programs.  
3. This is my preferred method of choice: Add a new reg key called "SystemComponent" with a dword value of 1 to HKLK:\Software\Microsoft\Windows\CurrentVersion\Uninstall\{3AB4D18D-98B3-41EF-94EA-DA587F282BB1} (or whatever key your Pulseway is in for that last part).  This will hide it from Add/Remove Programs.  So unless the user is more advanced or really determined to find it and remove it, this should stop most normal end users.  Value of 0 makes it appear again.  Very easy to just deploy via script to all machines Pulseway is on. 
 
I do think that Pulseway should provide an option to password protect the uninstall, but this was brought up years ago and hasn't been provided, so I don't think they plan on it any time soon. 

@AC_Martin_J I completely agree with your points.  Especially being able to right click the tray icon much like "get support" if they could be taken to the client portal. 
Unfortunately, seems as Pulseway wants to use the CP as a means to collect more money which I mean, I get it, everyone has to make their money but perhaps if it was more flexible I could see a cost, but currently it's very limited.  
 

I have an "onboarding" workflow set up that runs when a new machine is registered.   It determines if it's a workstation or server and then runs quite a number of custom scripts I created from installing some default software that I always deploy to my clients, such as additional remote access tool, Endpoint Protection as well as a few other installs.  
It also runs a few scripts that set certain aspects of the machines environment as well as filling in some custom fields I have in my portal that I use for additional data collection from devices.  
The client portal I've started to use more but it's admittedly limited.  However, 2 such use cases I use it for are..
1.  A customer purchases a new machine themselves and want me to manage it.  I let them log into the portal which displays a link to their client specific Pulseway installer.  They install it, then my onboarding workflow does the rest. 
2. Some of my clients have specific software applications that very infuriatingly have "known" issues that the software vendor refuses to currently fix, like a piece of the software disappearing off the screen and the "fix" is modifying some registry keys and a couple files.  I have a troubleshooter that lets the user having the issue run the script I wrote to auto fix the reg keys and files instead of having to rely on reaching out for help and waiting on a response.   

When you create a patch policy, just set it to Weekly, and then choose your days.  You can select more than one to repeat on.  So choose Saturday/Sunday.  
 

Going to bring this thread back to the top.  If anyone else feels that having the ability to input at run time a variable they declared as a custom field in their scripts, please upvote.  This is probably one of the single biggest improvements I want to see with Pulseway.  Custom variables should be able to be set to prompt at run for input.  We should also be able to set Customer level variables that are static and can be called in a given script.  
Here is the link to the feature request.  I did search and didn't find someone else asking about this, but I may have missed it. Either way, doesn't seem high on the list of votes so getting more attention to it would be great. 
https://pulseway.featureupvote.com/suggestions/189283/more-robust-input-and-site-variables