Difference between revisions of "Application"
From Veloopti Help
m |
m |
||
| Line 26: | Line 26: | ||
|} | |} | ||
| − | [[Category:Applications]] | + | [[Category:Concepts]] [[Category:Applications]] |
Revision as of 22:23, 18 July 2018
Home > An Overview > Concepts > Applications
1 Overview
Applications are one of the foundations of Veloopti. They are used to keep dashboards and events separate from and users within an organisation.
2 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, nodes, policies and actions that are within it. From here your role determines what you are able to do with them. There are five roles available within an application.
| Default application roles | |
|---|---|
| Role | Description |
| 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 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 |
| Read only | Has read only access to see dashboards and events. |