1,774
edits
Changes
m
no edit summary
== Overview ==
Applications are one of the foundations of means by which Veloopti for keeping keeps data, dashboards , actions and their permissions separate policies segregated within an organisation. Applications in your organisation are found by clicking on the Application menu item at the top of the Veloopti web siteconsole. Applications can be made a [[Favourites|favorite]] in the same manner as as dashboards are for quicker access to them.
== Selecting an application ==
Clicking on the Application menu item brings up the [[Application_view|application view]].
=== Actions Navigating applications ===The easiest way to navigate through your applications is to change the application through the breadcrumb. Use the drop down application menu [[file:Breadcrumb application navigation selection arrow.png|20px]] to select the other applications that you have access to. The below example contains an application called ''Application of Amazing things''{{See also. You can use the drop down menu to the right of the application name to select another. [[file:Breadcrumb application navigation.png|Action}}500px]] === Navigating components of an application === The below example shows the nodes of the ''Application of Amazing things''. Use the drop down menu to the right of the Node item to select between actions, dashboards, nodes, permissions, policies roles or users.Actions [[file:Breadcrumb application navigation.png|500px]] == Components of an application ==Components of an application are applications or commands that can able to be run on a server with a Veloopti agent from the Veloopti consoleviewed and configured depending upon your permissions. The command can return a result that will be displayed back to you after it is run
=== Visible to all application users ======= Dashboards ====
:''{{See also|Dashboard}}''
Dashboards can be created for the nodes in the application from the policies or API that are collecting metrics.
==== Nodes ====
:''{{See also|Node}}''
Nodes that have been added to the application appear here. Nodes are able to have application policies deployed to them, application actions associated with them and their metrics can be visible for display in a dashboard.
==== Users ====:''{{See also|User}}''Once a user is added to the application they are able to be added to roles within the application. === Visible only with appropriate permissions ======= Actions ====:''{{See also|Action}}''Actions are command line applications or commands that can be run on a server with a Veloopti agent. The application or command can return a result that will be displayed back to you after it is completed. ==== Permissions ====
:''{{See also|Permission}}''
Roles can be created, or deleted and modified herewith permissions applied to the role. After selecting a role permissions can be enabled or disabled.
==== Policies ====
:''{{See also|Policy}}''
[[Glossary_of_terms#P|Policies]] can be created, modified and deleted here. After being created policies are put into a policy group that can be associated with a node group for deployment.
==== Roles ===:''{{See also|Role}}''Users that are in the application can be put into a role here. === Users ===:''{{See also|User}}''Once a user is added to the applcation == Roles ==
:''{{TNT|Main|Application roles}}''
The role(s) one or more roles that you have in an application determines the things items presented that you are able to do within itperform. Everyone is able to see all events, users, and nodes, policies and actions that are within itin an application. From here your role determines what any additional permissions that you are able to do with themmay have. There are five default roles available within an application.
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
| Owner || There is one owner for each application. Along with the Application Administrator they are able to rename and delete the application. The owner and Application administrator is also able to grant and remove anyrole or notification group to another user of the application.
|-
| Administrator || Can do anything in t he the application that involves: users, policies, actions, events and notifications.
|-
| Power user || Power users are able to do everything the [Application name] Administrator can do except for:
| Operator || The date/time that the message will be removed from your message inbox
|-
| DashboardRead creator only || Can do anything that involves creating Has read only access to see dashboards and editing a dashboardevents.
|}