Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section helps you set up your organization-wise user database. After you set up the user database, you can create roles and groups, and can add users to such entities.

...

  1. Open the Users administration screen from MANAGE, Administration, Tools, and  click Users.
  2. Hover over the User in the list, click the  icon in the far left column, and click Edit Properties.
  3. On the Basic tab, perform one of the following actions:
    • Enter a new password and retype the password in the Change Password field. Click the Change Password button.
      Password change successful or policy violation message is displayed. 
    • Click Send Email. An email with a reset password link is then sent to the user. The user can click the link and can reset the password.

    The user password is reset.

...

  1. Open the web services user password administration screen from MANAGE, ADMINISTRATION, Tools , and  click Reset Web Services User Password.
  2. Search and select the web services user.
  3. Perform one of the following actions:
    • Enter the new password details and click Apply Changes.
    • Click Reset Password. An email with a reset password link is then sent to the user. The user can click the link and can reset the password.
    The web service user password is reset.

...

  • You cannot deactivate a role. The deleted roles are directly removed from the application.
  • A contact and a support group can participate in multiple roles.
  • The permission assignment to a role is not a part of role creation. The Assigned Permissions section is read-only and displays the permissions that are assigned to the current role. 
  • The system defined roles have a negative ID value. You cannot delete the system defined roles. For example, KB Analyst and KB Admin. 
  • You can delete a role. When you delete a role, the role record gets removed from the application. When a role is deleted, the relationships to contacts and groups that are related to the role are also lost. Therefore, permissions available to the contacts and support groups through that role are no longer available.

  • Do not create more than one role with the same name. The reason is that there could be a conflict in the recognition of the name by the system. However, ServiceAide Cloud Service Management (CSM) does allow you to create multiple roles with the same name.
  • Roles cannot be used for assignments. Roles are available only of managing permissions and for identifying recipients for a communication template. This behavior makes it possible to send the notification to all members of the role.

Verify the following prerequisites:

  • Support groups and contacts are configured.  

...