Difference between revisions of "Permissions"
m |
m |
||
Line 22: | Line 22: | ||
---- | ---- | ||
{| | {| | ||
− | | [[file:slider_right.png|30px]] | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] |
− | | Install | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | Install |
− | | The user can install an agent on a server by providing their username and password. | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can install an agent on a server by providing their username and password. |
|- | |- | ||
− | | [[file:slider_right.png|30px]] | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] |
− | | Upgrade | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | Upgrade |
− | | The user can initiate an agent to upgrade | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can initiate an agent to upgrade |
|- | |- | ||
− | | [[file:slider_right.png|30px]] | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] |
| Restart | | Restart | ||
| The users can stop an start the Veloopti agent | | The users can stop an start the Veloopti agent | ||
Line 45: | Line 45: | ||
---- | ---- | ||
{| | {| | ||
− | | [[file:slider_right.png|30px]] | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] |
− | | List all | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | List all |
− | | The user is able to view the complete list of applications in the application list view. | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user is able to view the complete list of applications in the application list view. |
|- | |- | ||
− | | [[file:slider_right.png|30px]] | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] |
− | | View all | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | View all |
− | | The user is able to enter all applications in the application list view. This gives the user a read only view of the Dashboards, users and nodes in the application. | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user is able to enter all applications in the application list view. This gives the user a read only view of the Dashboards, users and nodes in the application. |
|- | |- | ||
− | | [[file:slider_right.png|30px]] | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] |
− | | Create and Rename | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | Create and Rename |
− | | The user can create a new application and rename an existing one | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can create a new application and rename an existing one |
|- | |- | ||
− | | [[file:slider_right.png|30px]] | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] |
− | | Change application owner | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | Change application owner |
− | | | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can change an application owner to another user. |
NOTE: This permission allows the user to assume full rights over any application. As the Owner of an application is the only user that is able to delete an application that means that this permission is also the "Delete Application" permission. | NOTE: This permission allows the user to assume full rights over any application. As the Owner of an application is the only user that is able to delete an application that means that this permission is also the "Delete Application" permission. | ||
|- | |- | ||
Line 322: | Line 322: | ||
| Close Events | | Close Events | ||
| User can close an open event. | | User can close an open event. | ||
− | NOTE: Once | + | NOTE: Once an event is closed it cannot be re-opened. |
|- | |- | ||
|} | |} | ||
Line 333: | Line 333: | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Manage Node Groups | | Manage Node Groups | ||
− | | | + | | The user can add and remove node groups |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Add Node to Node Group | | Add Node to Node Group | ||
− | | | + | | The user can add a node to a node group |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Link Policy Group to Node Group | | Link Policy Group to Node Group | ||
− | | | + | | The user can link a policy group to a node group |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Link Action Group to Node Group | | Link Action Group to Node Group | ||
− | | | + | | The user can link an action group to a node group |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Remove Node from Application | | Remove Node from Application | ||
− | | | + | | The user can remove a node from an application |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Run action from Node | | Run action from Node | ||
− | | | + | | Users can run an action on a node. |
+ | NOTE: The user also needs to have the run Operator/Power User/Administrator permission in order for the action to be available to them. | ||
|- | |- | ||
|} | |} | ||
Line 364: | Line 365: | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| View Policies | | View Policies | ||
− | | | + | | The user can see all policies in the policies list and open them |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Manage Policies | | Manage Policies | ||
− | | | + | | The user can create, edit and delete policies |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Manage Policy Groups | | Manage Policy Groups | ||
− | | | + | | The user can create and delete policy groups. |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Add Policy to Policy Group | | Add Policy to Policy Group | ||
− | | | + | | The user can add policies to policy groups |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| List Policies on a Node | | List Policies on a Node | ||
− | | | + | | The user can see the policies that have been deployed to a node |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Deploy Policies | | Deploy Policies | ||
− | | | + | | The user can deploy policies |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Assign Action to Policy | | Assign Action to Policy | ||
− | | | + | | The user can assign an action to a policy. |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Manage Node Overrides | | Manage Node Overrides | ||
− | | | + | | The user can add a node override for a policy. This enables the node to have different thresholds from the policy defaults. |
|- | |- | ||
|} | |} | ||
Line 402: | Line 403: | ||
{| | {| | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
− | | Manage | + | | Manage User Groups |
− | | | + | | The user can create and delete user groups |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Add User to User Group | | Add User to User Group | ||
− | | | + | | The user can create and delete user groups |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Add / Remove user to Application | | Add / Remove user to Application | ||
− | | | + | | The user can add and remove users from the application |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Add User to Application Role | | Add User to Application Role | ||
− | | | + | | User can add other users to application roles |
|- | |- | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Edit Application Role Permissions | | Edit Application Role Permissions | ||
− | | | + | | The user can create, edit and delete application roles |
|- | |- | ||
|} | |} | ||
Line 430: | Line 431: | ||
| [[file:slider_right.png|30px]] | | [[file:slider_right.png|30px]] | ||
| Manage Dashboards | | Manage Dashboards | ||
− | | | + | | The user can create, edit and delete dashboards |
|- | |- | ||
|} | |} |
Revision as of 16:20, 17 January 2019
Contents
1 Overview
A central design point of Veloopti security is that no user has permission to perform any operation unless they have been specifically granted it. The purpose of granting a permission is to enable a user to perform a specific action. Permissions either extend globally to the whole of Veloopti, or locally to a single application. Each application has total control of its own permissions and they do not interfere with another application.
2 Design considerations
A central design point of Veloopti permissions is to empower the owner of an application to have everything they need to monitor their application. They should be able to write and deploy any monitoring for their application without being interfered by another application.
3 Roles and permissions
Permissions are bundled together and can appear in one or more roles.
Global permissions and application permissions
Global permissions reach to the entire Veloopti organisation and can extend into every application. Application permissions exist only in the application.
4 Global permissions
AGENTS
APPLICATIONS
EVENTS
LOGS
NODES
ORGANISATION
STORM RULES
View All | The user can view storm rules | |
Manage All | The user can create and edit storm rules |
POLICIES
USERS
DASHBOARDS
Manage all | Can be used in conjunction with the application "View all" global permission to empower a user to enter any application and modify the dashboards. |
5 Application permissions
ACTIONS
EVENTS
NODES
POLICIES
USERS
DASHBOARDS
Manage Dashboards | The user can create, edit and delete dashboards |
5.1 Owner
The role of owner has permanent permissions that cannot be revoked. Even if all roles are lost to everyone else the owner is still able to access the ones below. Once the role of owner is given to another user it cannot be taken back. If the role of owner is somehow lost to an organisation then contact Veloopti.
Description | Location | |||||
---|---|---|---|---|---|---|
Permissions | URL | Global options | Context options | Item options | Button | Other |
Change Owner | ap1.veloopti.com.au/organisation/index/special | Yes | ||||
Change Billing Administrator | ap1.veloopti.com.au/organisation/index/special | Yes | ||||
Edit Global and Application Role Permissions | ap1.veloopti.com.au/permissions | Menu item | ||||
Add Users to Global and Application Roles | ap1.veloopti.com.au//roles/index/ | Menu item |