Difference between revisions of "Application"
m |
m |
||
| Line 26: | Line 26: | ||
|} | |} | ||
| − | [[Category:Concepts]] [[Category: | + | [[Category:Concepts]] [[Category:Applications]] |
Revision as of 19:09, 15 November 2018
Home > An Overview > Concepts > Applications
1 Overview
Applications are used to grant permissions to a group of users to nodes, dashboards, actions, policies and events within your organisation. Once you have added the servers and users to an application, simply assign roles to the users and let them do the rest. The application roles give your users permissions to do various things such as configuring and deploying monitoring, running actions on servers, viewing events and more.
2 Application roles
- Main article: Application roles
The role(s) that you have in an application determines the things that you are able to do within it. Everyone is able to see all events, users and nodes that are in it. Beyond this your role determines what you are able to do. There are five default roles available within an application with any additional number able to be user created.
| Default application roles | |
|---|---|
| Role | Description |
| Owner | There is 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 or remove any role or notification group of another user of the application. |
| Administrators | Can do anything in the application that involves: nodes, users, policies, actions, events and notifications. |
| Power users | Power users are able to do everything the [Application name] Administrator can do except for: |
| Operators | The date/time that the message will be removed from your message inbox |
| View only | Able to see dashboards and events. |