Administration Guide

Create and Maintain Customer Accounts

On this page

A customer account, shown in the Settings App as SSP customer, gives an end user access to the Self Service Portal. A customer account does not use a license seat, and security roles do not apply to it: its access level decides whose tickets and service requests the customer sees in the portal in addition to their own. For the account types, the access levels, and how an account relates to a person, see Accounts.

Customer accounts can come into being in these ways:

  • An administrator creates them in the Admin Center or in the Settings App.
  • End users register themselves in the portal. Depending on the self-registration settings, the account is created at once, or the request waits as a pending registration until an administrator approves it. Setting up self-registration is described in Self-Registration.
  • An Active Directory synchronization job creates them when its option to create Self Service Portal accounts is on. A job created in the Settings App has this option on by default.

Before you begin

  • The person. The account belongs to an existing person. In the Settings App, a Windows Native account can instead take its person from Active Directory.
  • The login. A Windows Native account uses a Windows account as its login. A Standard or Single Sign-On account without a password can sign in only by single sign-on. If such an account's login is not an e-mail address, you are warned first.
  • The password policy. When the password policy is enforced for all users or for SSP customers only, a password you set is checked against it. In the Admin Center, this applies to a password you enter in the account-creation wizard, in Change Password, or in Modify Login.
  • Administrative rights. In the Settings App, the Users & Security group, which holds the accounts, and the Self Service Portal group, which holds the Self-Registration page, are each gated by their own administrative right. See Permissions Reference.

A customer can sign in while the account is active and the person's status is not Inactive. When the person's status becomes Inactive, the person's customer accounts are disabled, and they stay disabled when the person is made active again.

In the Admin Center

Customer accounts are on the Accounts tab of the Accounts and Roles page. For pending self-registrations, see Approve or reject pending registrations in the Settings App.

Create a customer account

  1. Open the account-creation wizard.
  2. Choose the SSP account type.
  3. Choose the authentication: Windows Native or Standard or Single Sign-On.
  4. Enter the login:
    • For Windows Native, specify the Windows account on Select Windows Account.
    • For Standard or Single Sign-On, enter the username on Credentials. To let the customer sign in with a password, select Allow password authentication and enter the password. If you leave password authentication off and the username is not an e-mail address, a warning appears: click Yes to turn password authentication on and stay on the step, or No to continue without a password.
  5. Click Next. The wizard checks that the username is not already in use and, when you entered a password, validates the password on the server. If the password is refused, an error dialog describes the requirements and the wizard stays on Credentials.
  6. On Associate Person, pick the person the account belongs to. For a customer account, the picker searches all persons, not only technicians.
  7. On Select Access Level, choose Regular user, Manager, Group manager, Department manager, or Organization manager. Each choice has its own helper text.
  8. Finish the wizard. The username is checked for uniqueness once more before the account is created.

A customer account does not go through Select Technician Type or Assign Roles. Use Back to change the account type or the authentication choice without leaving the wizard. Closing the wizard at any step asks you to confirm, even when you have changed nothing.

If you create the account with Allow password authentication cleared, it has no password.

Edit a customer account

The account editor of a customer account has only the General tab. The editor treats a login that contains a backslash as Windows Native and any other login as Standard or Single Sign-On.

On the General tab, Make Active / Make Inactive changes the account's status; see Accounts for what disabling does. The button is not shown on your own account.

Change the login

Use Modify Login in the account editor. The login is checked against the authentication type you select:

  • Standard or Single Sign-On refuses a username that contains a backslash once you have changed the form. If Allow password authentication is off and the username is not an e-mail address, a warning offers to turn password authentication on or to continue without it.
  • Windows Native requires a backslash and shows an error when it is missing.

For a customer account, the person field is not limited to technicians. Clearing Allow password authentication removes the account's password when you save.

Set or change the password

In the account editor:

  • Change Password is shown when the account has password authentication. Enter the new password and click OK. The password is validated on the server as in the wizard, and a refused password shows the same error dialog. If you have typed nothing, OK only closes the drawer.
  • Set Password is shown when the account has no password. If the username is an e-mail address, you are asked first: "After you set a password, the user will also be able to log in with the username and password. Continue?" Click Yes to enter the password.
  • For a Windows Native account the button is disabled.

Convert a customer account to a technician account

  1. Open the customer account and use the type-conversion button on the General tab. On your own account, an information dialog appears and the conversion stops.
  2. Confirm the conversion.
  3. If the person is not marked as a technician, a second warning names the person. Click Yes to mark the person as a technician, or choose the other option to change only the account type. The person is changed right away, even if you do not save the account.
  4. Save the account. The account's new type is saved only with the account.

When the named licenses are used up and the license allows no concurrent users, the conversion is refused with a license error.

A technician account without a security role cannot be saved: the message "Technician accounts must have security roles. Please grant at least one role to this account." appears, and OK takes you to Member Of. See Security Roles.

Delete customer accounts

On the Accounts tab, select one or more accounts and click Delete.

In the Settings App

Customer accounts are under Users & Security > Accounts and Roles > Accounts, listed together with technician accounts as SSP customer. The toolbar offers New, Edit, and Delete.

Create a customer account

  1. Open the New Account wizard. It starts on Welcome. Click Next to move from page to page.
  2. On Select Account Type, choose SSP customer.
  3. On Select Authentication Type, choose Windows Native or Standard or Single Sign-On.
  4. Enter the login:
    • For Standard or Single Sign-On, fill in Username:. To let the customer sign in with a password, select Allow password authentication and fill in Password: and Confirm:. If the username is not an e-mail address and you leave the check box clear, a warning recommends password authentication. Click Yes to select the check box and stay on the page, or No to go on without a password.
    • For Windows Native, specify the Windows account on Select Windows Account. Then, on Import Person from Active Directory, select Import user information from Active Directory to take the person from the directory.
  5. On Associate the Account with a Person, select the person the account belongs to. The Select Person list offers active persons.
  6. On Select Access Level, under "Select a user's access level to the Self Service Portal.", choose the level in the User access level group.
  7. On Ready to Create, click Next. The account is created, and Account Created confirms it.

The wizard refuses to go on when the username is empty or already used, when the two passwords differ or the password does not meet the password policy, when the person read from Active Directory has no full name, or when no person is selected. It does not create a SQL Server login for the account.

Neither login page refuses a login whose form contradicts the authentication type you chose, as Modify Login does. The authentication type is not stored with the account: it is derived later from the login and from whether the account has a password, and a login that contains a backslash counts as a Windows login.

When the wizard is given a Windows login in the DOMAIN\user form, it creates a new person from the directory user, or uses the existing person the directory user matches and clears its Inactive status. When you pick the person yourself instead, the wizard changes nothing on the person. Creating a customer account leaves the person's technician flag as it is.

Edit a customer account

Select the account and click Edit. The User Account window opens. For a customer account, the General tab shows the User access level group with five levels, top to bottom, each with its explanation line. The wizard's Select Access Level page shows the same group.

  • Regular User: "Regular users can view and update only their own Tickets."
  • Manager: "Managers can view and update their Tickets and Tickets submitted by other users for whom they are managers."
  • Group Manager: "Group managers can view and update their Tickets and Tickets submitted by members of groups they manage."
  • Department Manager: "Department managers can view and update their Tickets and Tickets submitted by other users from the same organization."
  • Organization Manager: "Organization managers can view and update their Tickets and Tickets submitted by other users from the same organization, including its sub-organizations."

The chosen level is saved with the account. The License group and Member Of, Effective Permissions, and Workflow Actions are not shown for a customer account.

To change the login or the person, use Modify Login:

  • The form preselects Windows when the login contains a backslash and Standard or Single Sign-On otherwise.
  • Choose Windows or Standard or Single Sign-On. A login with a backslash is refused for Standard or Single Sign-On, and a login without the DOMAIN\UserName form is refused for Windows.
  • Find opens the Windows user picker for Windows; picking an account of the local computer gives a plain name without the computer name. For Standard or Single Sign-On, Find searches Active Directory and fills in the user's e-mail address.
  • For Standard or Single Sign-On, Allow password authentication decides whether the account keeps a password. The hint reads "Username for password authentication or email address for SSO". Clearing the check box removes the stored password when you save. If the login is not an e-mail address and the check box is clear, a warning says the login cannot be used for Single Sign-On authentication and asks whether to allow password authentication now: Yes selects the check box and takes you to the password field, No saves without a password, and Cancel keeps you in the window.
  • The person box's button opens Select Person, which is not limited to technicians.

To set a new password, click Change Password. The command is not available for a Windows login in the DOMAIN\user form. The password is checked against the password policy when the policy is enforced for all users or for SSP customers. On an account without a password whose login is an e-mail address, Set Password first asks whether the user should also be able to sign in with a password.

Convert between customer and technician

The User Account window offers Convert to Technician and Convert to SSP. Both ask for confirmation first.

  • Convert to Technician: the confirmation says the access level will be set to Regular User. The conversion needs a free named seat or a license with concurrent users. Otherwise the message "Unable to make this SSP account a Technician account. You have exceeded the license limit for named Technician accounts." appears. If the person is not marked as a technician, the window offers to mark it: click Yes or Cancel. The conversion goes ahead either way.
  • Convert to SSP warns: "All permissions granted to this account via its membership in security roles will be lost". When you save, the account's role memberships are removed and the access level shown in the window is saved. The account you are signed in with cannot be converted to SSP: the message "Cannot convert the account that you are currently logged in to." appears.

Enable, disable, or delete accounts

To enable or disable accounts, see Accounts.

To delete accounts, select them and click Delete. Confirm at "Are you sure you want to delete the selected item?", or, for several accounts, "Are you sure you want to delete N selected items?". The accounts are deleted one at a time, and each one only when you have the permission to delete it:

  • An account with an open session is skipped with the message "You cannot delete the account "<login>" because it is currently in use." This is also the message you normally see for your own account; when your own account has no open session, the message is "You cannot delete this account, since you are currently using it for accessing the Settings."
  • When an account other than the last one fails, you are asked "Would you like to continue removing the remaining records?": click Yes, Yes to All, or No.
  • After deleting several accounts, the Settings App reports how many of the selected items were deleted: "N of M items have been deleted."

Approve or reject pending registrations

When the portal requires self-registered accounts to be authorized, a registration waits as a pending request. Until a request is approved, no account exists for it, and the customer cannot sign in. No person exists for it either, except for a request stored by a product version earlier than 7 (see below).

The Self-Registration page shows the Pending registrations group when Enable self-registration and Self-registered accounts must be authorized by the manager are both selected, and otherwise only while at least one request is waiting.

  1. Go to Self Service Portal > Self-Registration.
  2. In the Pending registrations group, select one or more requests. The list does not show the passwords of the requests.
  3. Do one of the following:
    • Click Open to review a request. You can approve or reject it from the review form as well.
    • Click Approve to create the accounts.
    • Click Reject to delete a request. Only the request is deleted, except for a request stored by a product version earlier than 7 (see below). In the review form, Reject checks that you have the permission to delete and asks "Are you sure you want to delete this item?"

When you approve a request, the Settings App:

  1. Creates the person with the create-Person action set up for the portal's self-registration, unless the request already has its person (a request stored by a product version earlier than 7).
  2. Creates the customer account with the password the customer chose when registering.
  3. Queues an account notice, the Registration Confirmation message, to the person's primary e-mail address. The notice does not contain the password; in its place it reads "Use the password that you specified during the registration."
  4. Removes the request from the list.

If a step fails, for example because the person has no primary e-mail address, the person and the account that the approval created are deleted, and the request stays in the list. When you approve several requests and one fails before the last, the error is shown with "Would you like to continue approving the remaining records?": click Yes, Yes to All, or No. No stops the run. When you selected more than one request, the Settings App then reports how many of them were approved: "N of M items have been approved."

A request stored by a product version earlier than 7 already has its person. Approving it does not create another person, and rejecting it deletes that person as well as the request. Opening such a request shows the person, read-only, instead of the review form.

After approval, the customer signs in as described in Sign In to the Portal.

How self-registration in the Self Service Portal creates accounts

  • When approval is not required, the portal creates the person with the configured create-Person action, then the customer account for it, and queues the account notice, the Registration Confirmation message with the password the customer typed, to the person's primary e-mail address.
  • When approval is required, the request waits in Pending registrations until you approve or reject it.
  • In both cases, the password is checked against the password policy before anything is stored. A registration is refused when its e-mail address already belongs to a person, or when its login is already used by an account or by another pending request.