Jump to content

PatchManagement - Agent Status

Gary Haberl

Recommended Posts


We install RMM agents to all systems from one account, and then share the systems to other accounts to manage who manages what.

The Patch Management "Agent Status" only works for the user who installs the agent.  BUT, creating policies can be done by anyone.  And the Policies are shared between all users.

Is there a reason only the person who installed the agent can apply Patch Management via the Agent Status link?

Also...The "Patch Policy" link on the Android App does not show up unless you are the person who installed the RMM on the client system.  But all other features are there.

I'm thinking a little more work is needed on this so all techs can use the patch management. Or is this written this way for a reason?


Link to comment
Share on other sites


We have a similar setup with the accounts and facing this issue. 

Hoping this will get addressed soon so that delegated accounts are able to see same settings and configurations as the one used for agent installations.

Best regards


Link to comment
Share on other sites

  • Administrators


We are honouring the existing security system in place to prevent other users from controlling security critical features such as antivirus / os patch deployment status, scripts and tasks as changes might accidentally affect systems that you are not aware.

There are plans on revamping the user security systems at Pulseway to introduce user groups and access levels which will allow you to provide full access to the entire Pulseway feature set for other users. 


Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...