Difference between revisions of "Permissions"
m (Update with current information) |
m |
||
| Line 24: | Line 24: | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | Install | | style="vertical-align:top;border-bottom:0.5px solid gray;" | Install | ||
| − | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can install an agent on a | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can install an agent on a computer by providing their username and password. |
|- | |- | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | ||
| Line 80: | Line 80: | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | View internal Veloopti events | | style="vertical-align:top;border-bottom:0.5px solid gray;" | View internal Veloopti events | ||
| − | | style="vertical-align:top;border-bottom:0.5px solid gray;" | User can view events that have been created internally by | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | User can view events that have been created internally by Veloopti agents. These can be used to help diagnosing agent issues. |
|- | |- | ||
|} | |} | ||
| Line 118: | Line 118: | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | Deploy policies | | style="vertical-align:top;border-bottom:0.5px solid gray;" | Deploy policies | ||
| − | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can deploy all application policies to | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can deploy all application policies to nodes whether they have access to the application or not. |
|- | |- | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | ||
| Line 172: | Line 172: | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | Manage Auto Discovery | | style="vertical-align:top;border-bottom:0.5px solid gray;" | Manage Auto Discovery | ||
| − | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can manage the auto discovery options for discovering application on | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can manage the auto discovery options for discovering application on computers |
|- | |- | ||
|} | |} | ||
| Line 287: | Line 287: | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | Assign Action to Action Group | | style="vertical-align:top;border-bottom:0.5px solid gray;" | Assign Action to Action Group | ||
| − | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can add actions to actions group. This allows the action to be available to be run on any | + | | style="vertical-align:top;border-bottom:0.5px solid gray;" | The user can add actions to actions group. This allows the action to be available to be run on any node in the application. |
|- | |- | ||
| style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | | style="vertical-align:top;border-bottom:0.5px solid gray;" | [[file:slider_right.png|30px]] | ||
Revision as of 17:59, 11 May 2020
Home > Administration > User Administration > Permissions
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
|
Install | The user can install an agent on a computer by providing their username and password. |
|
|
Upgrade | The user can initiate an agent to upgrade |
|
|
Restart | The users can stop an start the Veloopti agent |
|
|
Create installation token | The user can create an installation token that can be used to install an agent that does not require a username and password. |
APPLICATIONS
|
|
List all | The user is able to view the complete list of applications in the application list view. |
|
|
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. |
|
|
Create and Rename | The user can create a new application and rename an existing one |
|
|
Change application owner | 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. |
EVENTS
|
|
"View all | "The user can view all events for all applications |
|
|
Manage all | The user can change the status and set the event to closed |
|
|
View internal Veloopti events | User can view events that have been created internally by Veloopti agents. These can be used to help diagnosing agent issues. |
LOGS
|
|
View Audit Logs | The user can view the logs that are created any time a change is made in Veloopti |
|
|
View Notification Logs | The user can view the logs that are created any time a notification is sent. |
|
|
View Security Logs | The user can view logs that are created any time a user does something in Veloopti. This included logon and logout activities. |
|
|
View Billing Logs | The user can view the logs that relate to billing |
NODES
|
|
View all | The user can view all nodes in the node list. They also can view the node properties. |
|
|
Deploy policies | The user can deploy all application policies to nodes whether they have access to the application or not. |
|
|
Add Node to Applications | The user can add a node to any application in the organisation.
NOTE: The user does not need to have permission to view the application to add it. |
|
|
Relabel Nodes | The user is able to change the label of the node |
|
|
Remove Nodes | The user is able to remove the node from the organisation |
ORGANISATION
|
|
Manage Node Billing Plan | The user is able to change the billing plans for any node that they can see |
|
|
View Organisation Billing Details | The user is able to view the invoices for the organisation |
|
|
View Extra Details | x |
|
|
Change Default Settings | The user can change the organisation default settings of: Language; Time Zone and Default new node plan. |
|
|
Manage Schedules | The user can change the schedules |
|
|
Add Users to Global and Application Roles | User can add and remove users in Global and Application roles.
NOTE: The user needs to be granted access to the application before they can add or remove users from the applications roles. |
|
|
Edit Global and Application Role Permissions | User can edit a role by adding or removing permissions from it. They also can create new roles.
NOTE: The user needs to be granted access to the application before they can add or remove permissions from the applications roles. |
|
|
Manage Auto Discovery | The user can manage the auto discovery options for discovering application on computers |
STORM RULES
|
|
View All | The user can view storm rules |
|
|
Manage All | The user can create and edit storm rules |
POLICIES
|
|
Manage all | Allows the user full permissions to policies for any application that they are able to view. Can be used in conjunction with the application "View all" global permission to empower a user to enter any application and modify the policies. |
USERS
|
|
Add Users to Global Roles | The user can add and remove users from global roles |
|
|
Invite User to Organisation | The user can send an invitation to an external email address to add them to their organisation |
|
|
Remove User from Organisation | The user can remove any user, except for the organisation owner, from the organisation |
|
|
View Active User Sessions | The user can view active user sessions for all users |
|
|
View Expired User Sessions | The user can view expired user sessions for all users |
|
|
Kill any Users Session | The user can kill any users active session. |
|
|
Add User to Application | The user can add another user to any application that they can view |
|
|
Add / Remove user from Application User Group | The user can add or remove a user from an application user group that they can view |
|
|
Add Other Users to this Role | Allows any member of the role to add another user to the role. This means that the members of the role are able to self manage rather than having to rely on someone with the Global "Assign User to Global Role" role. |
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
|
|
View all actions | The user can view all of actions in the application |
|
|
Run Operator Actions | The user can run actions that have an operator level permission. |
|
|
Run Power User Actions | The user can run actions that have a Power User level permission.
Note: This does not mean that users have permission to run an operator level action. |
|
|
Run Administrator Actions | User can run actions that have an Administrator level permission.
Note: This does not mean that users have permission to run an Operator or Power User level action. |
|
|
Manage Actions | The user is able to create, edit and delete actions. |
|
|
Assign Action to Action Group | The user can add actions to actions group. This allows the action to be available to be run on any node in the application. |
|
|
Manage Groups | The user can add and remove action groups |
EVENTS
|
|
View Events | The user can view events for the application |
|
|
Edit Event Description | The user can change the event description for an open event.
NOTE: Under no circumstances can the description for a closed event be changed. |
|
|
Change Event Severity | The user can change the event severity for an open event.
NOTE: Under no circumstances can the severity for a closed event be changed. |
|
|
Run Action from Event | The user is able to run an action on a node from an event.
NOTE: The user also needs to have the run Operator/Power User/Administrator permission in order for the action to be available to them. |
|
|
Close Events | User can close an open event.
NOTE: Once an event is closed it cannot be re-opened. |
NODES
|
|
Manage Node Groups | The user can add and remove node groups |
|
|
Add Node to Node Group | The user can add a node to a node group |
|
|
Link Policy Group to Node Group | The user can link a policy group to a node group |
|
|
Link Action Group to Node Group | The user can link an action group to a node group |
|
|
Remove Node from Application | The user can remove a node from an application |
|
|
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. |
POLICIES
|
|
View Policies | The user can see all policies in the policies list and open them |
|
|
Manage Policies | The user can create, edit and delete policies |
|
|
Manage Policy Groups | The user can create and delete policy groups. |
|
|
Add Policy to Policy Group | The user can add policies to policy groups |
|
|
List Policies on a Node | The user can see the policies that have been deployed to a node |
|
|
Deploy Policies | The user can deploy policies |
|
|
Assign Action to Policy | The user can assign an action to a policy. |
|
|
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. |
USERS
|
|
Manage User Groups | The user can create and delete user groups |
|
|
Add User to User Group | The user can create and delete user groups |
|
|
Add / Remove user to Application | The user can add and remove users from the application |
|
|
Add User to Application Role | User can add other users to application roles |
|
|
Edit Application Role Permissions | The user can create, edit and delete application roles |
DASHBOARDS
|
|
Manage Dashboards | The user can create, edit and delete dashboards |
5.1 Owner
After creating an organistion the user is given both the roles of Owner and Billing Administrator. The role of Owner has permanent permissions that cannot be modified. The role of Owner cannot be renamed or deleted. The Owner is able to select another user to replace them and replace them as the Owner. The selected user is then able to accept or reject the role of Owner. If the new user accepts the role of Owner then any previous Owner is not able to select themselves to take the role of Owner again. Once the role of Owner is given and received to another user it cannot be changed except by the current Owner. If the use account that has the role of owner is somehow lost then contact Veloopti. The Owner always has access to the below permissions.
| Permissions | URL | |
|---|---|---|
| Change Owner | ap2.veloopti.com.au/organisation/index/special | |
| Change Billing Administrator | ap2.veloopti.com.au/organisation/index/special | |
| Edit Global and Application Role Permissions | ap2.veloopti.com.au/permissions | |
| Add Users to Global and Application Roles | ap2.veloopti.com.au//roles/index/ |