Changes

Applications are used to grant permissions to a group self contained collection of monitoring settings. Application roles give the users capabilities to nodes, dashboards, actions, policies and events within your organisationdo various things. Once you have Servers are added the servers and users to an application, simply assign roles to where they have various monitoring settings applied through the users and let them do the restuse of groups. The Users are added to an application where their roles give your users grant them permissions to do various things such as configuring in the application like write and deploying monitoring, running deploy policies or run actions on servers, viewing events and more.

== Application roles = Nodes ===:''{{TNT|Main|Node}''A node is a network endpoint. A server is a computer that has a Veloopti agent installed on it. Once a node is in Veloopti it can be added to any number of applications. The node has policies deployed to it according to the application node groups it is a member of. Actions are able to be run on a node according to the application node groups that it is a member of. === Actions ===:''{{TNT|Main|Action}}''An action is a executable binary or script that can be run locally on a node that has a Veloopti agent installed on it. An action can be initiated manually through the Veloopti GUI directly from a node; or manually and automatically through an event that is received from the node. Actions that are manually initiated on a node have three levels of permissions: Operator; Power User; and Administrator. Each level is granted through a user role. === Dashboards === === Policies ===A policy is monitoring configuration setting that are deployed to one or more groups of servers in the application. The servers send metric data and events that are visible to the users of the application. Policies deployed to a node can only be edited from the application that they reside in. === Roles ===

The An application role(s) is a collection of permissions that you have give to a user the ability to perform certain things in an the application determines . The '''edit roles''' drop down menu allows for the things that you are able to do within it. Everyone is able to see all events, users creation and nodes that are in it. modification Beyond this your of a role determines what you are able . The '''Assign roles''' drop down menu allows for users to dobe added or removed from roles. There are five four default roles available within an application which users with sufficient permissions are able to edit or delete; and you are able to create any additional number able to be user createdbeyond this.

| Owner || Although not granted in the same way as the other roles an owner is an important role of an application. There is only one owner of each application. Along with the Application Administrator they are able to rename the application. The owner and application administrator is also able to grant add or remove an application user to any role or notification group of another user of . It is also the only role that is able to delete the application.

| Administrators || Can do anything in the application that involves: nodes, ; users, ; policies, ; actions, ; events '''and''' notifications.

| Power users || Power Can add users are able to do everything the [Application name] Administrator application ande can do except for: manage user groups. Can also manage policies and dashboards. Can view all actions and run operator and operator actions. Can view policies and can put policies and nodes into outage. Has full control over events. Able to see all users, nodes and dashboards.

| Operators || The date/time that the message will be removed from your message inbox Can run operator actions. Can view policies and can put policies and nodes into outage. Has full control over events. Able to see all users, nodes and dashboards.

| View only || Able to see all events, users, nodes and dashboards and events.