After creating a Privilege-based user group, you can assign privileges to the Axeda Applications to that user group. Users assigned to the user group inherit the group's privileges. The ability for a user to see a page or object or select a link in the Axeda Application pages depends upon the privileges assigned to that user's user group.
Many of the privilege descriptions provided in the topics listed below show Hierarchy and Other Requirements or Considerations, which provide further information for a privilege, as follows:
o Hierarchy - Explains the relationship between some of the Axeda objects as it relates to user group privileges. The User hierarchy is shown below.
o Other Requirements or Considerations - If the ability to perform an activity is provided by more than one privilege, the additional privilege requirements are listed.
A User is assigned to User Group; a Delegated Admin Unit and the Delegated Admin Unit Administrator are also assigned to a User Group, |
|||
|
A User Group is assigned to an Asset Group, |
||
|
|
An Asset Group assigned to a Model or another Asset Group, |
|
|
|
|
A Model assigned to Gateways and Assets, to which Organizations and Locations are assigned. |
Each user can be defined in one or more user groups. Each user group can contain one or more users. Each Asset Group can have one or more assigned user groups. Each Model can be associated with one or more Asset Groups (which contain one or more assets). Each gateway or asset has a single associated model, and associated organizations and locations.
If a user logged into the Axeda Applications attempts to perform an operation for which he or she does not have the required privileges (based on user group assignments), then the functionality is not shown or is disabled, or the following message is shown:
"You have attempted to perform an operation for which you lack sufficient privileges. Please contact your administrator for more information."
Note: Most "Edit" privileges require the corresponding "View" privilege as well. For example, you cannot edit asset groups unless you have all of the following privileges: Administration - View, Administration - Asset Group - Edit, and Administration - Asset Group - View.
For the most part, privileges are aligned with applications; however, some activities are available in more than one application. In these instances, the same privilege may govern the activity in both applications. Such activities include deploying software packages, editing information about organizations and locations, and running scripts.
Follow the links below to view details about the privileges for the standard Axeda Applications and their features:
o Access Application privileges
o Administration Application privileges
§ Partner Login privileges (part of Administration application)
o Configuration Application privileges
o Report Application privileges
o Service Application privileges
o Software Management Application privileges
Follow the links below to view details about the privileges for the optional Axeda Applications and features:
o Dashboard Application privileges
o Preventive Maintenance Application privileges
o Usage Application Privileges
o ConnectedConfiguration privileges
To run Axeda Web services successfully, certain privileges must be set for the applications. The set of privileges for Axeda Applications user and Web services users is the same; however, there are a few additional privileges that apply to Web service operations only. See to Web Services privileges for those privileges.