[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

AIM User Privileges

The AIM application enforces user privileges so that users can only have access the information to which they have privileges. Table 47 defines the AIM user privileges.

Table 47: AIM User Privileges

Privilege

Description

AIM Admin Setting

AIM administrators can perform the following tasks:

If the logged in user does not have Admin privileges, these settings can only be viewed:

  • Connect AIM to JSS
  • Perform alert registration
  • Set archive locations incident detection interval
  • Set up and manage organizations
  • Set up and manage licensing
  • Create, edit, and delete trap destinations
  • Create, edit, and delete users
  • Create, edit, and delete user groups
  • Create, edit, and delete device groups
  • Associate device groups
  • Associate user groups

Ownership

Three levels of AIM user ownership are provided that the administrator can use when assigning new user privileges. See Table 46.

Delete Incident

AIM user can delete incidents in Incident Manager.

Reaction Policy

AIM user can manage all the policies he/she owns. It includes creation, deletion, disable, and enable policies. The policy will automatically be owned by the user who created it. If a user is deleted from AIM, all policies belonging to that user will be automatically deleted as well.

Submit Case

AIM user can submit any unassigned incidents to JSS.
[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]