Administration Guide

Create and Maintain Technician Accounts

On this page

A technician account lets a technician sign in to Alloy Navigator. It belongs to a person, carries a Named or Concurrent license type, and gets its permissions from its security roles. For the account types and how an account relates to a person, see Accounts.

You create and maintain technician accounts in the Admin Center or in the Settings App.

Before you begin

  • The person. For an account you create by picking a person, the person must be active and marked as a technician: the person lists of the account wizards and of Modify Login offer only such persons for a technician account. In the Settings App, the wizard's Select Person window can also create a missing person when a create action for persons is available, and a Windows account can instead take its person from Active Directory.
  • A free license. A named account needs a free named seat in the license; only active named technician accounts count against it. The number of concurrent accounts is not limited: the license's concurrent users limit how many technicians with concurrent accounts are signed in at the same time, and a technician signed in to two applications at once takes at most one concurrent seat.
  • Roles. A technician account needs at least one security role; see Security Roles. Roles also carry the technician's access scope; see Access Scope: Organizations and Workspaces.
  • The login. The authentication type is not stored with the account; it follows from the login and the password:
    • Windows Native: the login is a Windows account in the DOMAIN\user form, and the technician signs in with Windows credentials.
    • Standard or Single Sign-On: the login contains no backslash. With a password, the technician can sign in with the login and password. An account without a password can sign in only by single sign-on; for how a single sign-on user is matched to the login, see Single Sign-On. Both applications warn when you leave out the password for a login that is not an e-mail address.
  • The password policy. When the password policy is enforced for technicians, every password you set here is checked against it; see Password Policy.

A technician account can sign in only while the account is active and its person's status is not Inactive.

In the Admin Center

Technician accounts are on the Accounts tab of the Accounts and Roles page, beside the Roles and Applications tabs.

Create a technician account

  1. On the Accounts tab, start a new account. The account-creation wizard opens on its Welcome step.
  2. On Select Account Type, choose Technician. The choice is disabled, and the step shows the license-limit message, when the named licenses are used up and the license has no concurrent users.
  3. Choose the authentication type: 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 technician 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, that the password meets the password policy. If the password is refused, an error dialog with OK and Help lists the requirements the password does not meet, or shows the server's own message when no requirement is named, and the wizard stays on Credentials.
  6. On Associate Person, pick the person the account belongs to. The list offers only active persons marked as technicians.
  7. On Select Technician Type, choose Named or Concurrent. The step preselects Concurrent, or Named when the license has no concurrent users. When the named licenses are used up, Named is disabled; otherwise, when the license has no concurrent users, Concurrent is disabled. Each case shows its own license message.
  8. On Assign Roles, add at least one security role. Without one, an error dialog repeats the step's instructions and the wizard does not go on.
  9. Finish the wizard. The username is checked for uniqueness once more before the account is created.

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.

When you create or save an active technician account, the Admin Center refuses it if the account is named and the active named accounts would exceed the license's named users, or if the license value for the account's type (named or concurrent users) is 0. In both cases the page shows its general error message. Customer accounts and inactive accounts are not counted.

Edit a technician account

Select exactly one account on the Accounts tab and click Edit. A technician account has four tabs:

  • General: the license type, the status, and the account type.
  • Member Of: the security roles the account is a member of.
  • Effective Permissions: the permissions the account has through its roles, in the columns Name, Description, Allow, and Restricted. In Allow and Restricted, a checkmark means the permission itself has that setting; a filled square means it does not, but at least one permission under it does. If you have changed Member Of without saving, opening Effective Permissions asks "The record must be saved before proceeding with this action. Would you like to save the record now?" Yes saves and, when the save succeeds, opens Effective Permissions; No closes the question and keeps your unsaved changes.
  • Workflow Actions.

An account without roles 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. The message also offers Help.

On the General tab, License Assignment holds the account's license type: Named user or Concurrent user. A choice is disabled when the license has no room for that type and the account did not already have that type when you opened it:

  • Named user is disabled when the active named accounts have reached the license's named users, or when the license has no named users.
  • Concurrent user is disabled when the license has no concurrent users, or when the license information is missing.

The section then shows "License type change is unavailable. The maximum number of named accounts has been reached. Disable or delete another named account first, or contact support." or its concurrent counterpart, "License type change is unavailable. The maximum number of concurrent accounts has been reached. Disable or delete another concurrent account first, or contact support." The concurrent message also appears on a license with no concurrent users, where no count is involved.

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. If you activate an inactive account whose license type is not available, the status switches back to inactive: a named account when the named licenses are used up, a concurrent account when the license has no concurrent users. This happens only while the account keeps the license type it had.

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.

Clearing Allow password authentication removes the account's password when you save. After that, no password sign-in works for the account until you set a new password. The person field offers only active persons marked as technicians.

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 checked against the password policy, and a refused password shows the same error dialog as the wizard. 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 SSP 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. On Member Of, add at least one security role. A technician account without roles cannot be saved.
  5. Save the account. The account's new type is saved only with the account.

The Admin Center does not convert the account when the license has neither a free named seat nor concurrent users: a license error appears instead.

Delete technician accounts

Select one or more accounts on the Accounts tab and click Delete.

In the Settings App

Technician accounts are under Users & Security > Accounts and Roles > Accounts, where technician and SSP customer accounts are listed together. The account type reads Technician (Named), Technician (Concurrent), or SSP customer; service accounts and API accounts are not listed. The toolbar offers New, Edit, and Delete.

Create a technician account

  1. Click New. The New Account wizard opens on Welcome. Click Next to move from page to page.
  2. On Select Account Type, choose Technician.
  3. On Select Technician Type, choose Concurrent or Named. The page appears only when the license has both named and concurrent seats. Otherwise the account is Named when the license has named seats, and Concurrent when it does not.
  4. On Select Authentication Type, choose Windows Native or Standard or Single Sign-On.
  5. Enter the login:
    • For Standard or Single Sign-On, fill in Username:. To let the technician sign in with a password, select Allow password authentication and fill in Password: and Confirm:. Without a password the account can sign in only by single sign-on; if the username is not an e-mail address, 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 account on Select Windows Account, in the DOMAIN\user form. The Import Person from Active Directory page follows, with the Import user information from Active Directory check box.
  6. On Associate the Account with a Person, select the person the account belongs to. For a technician account, the Select Person list offers only active persons marked as technicians, and nothing on the person is changed. Double-click a row to select that person and close the window. If the person does not exist yet, the New menu of the window lists the create actions for persons: choosing one opens the action's form, and the new person can be created without leaving the window. When no create action is available, the menu shows the disabled item No Actions.
  7. On Assign Roles to Technician, add at least one role.
  8. 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 by another account.
  • The two passwords differ, or the password does not meet the password policy.
  • The person read from Active Directory has no full name.
  • No person is selected.
  • No role is assigned.
  • On Ready to Create, the account is Named and the license's named seats are used up.

The wizard does not check that the login matches the authentication type you chose. The choice itself is not stored: later, the account is treated as a Windows account when its login contains a backslash, and as a standard account when it does not.

When the wizard is given a Windows login in the DOMAIN\user form, it creates a new person from the directory user and marks it as a technician, or, when the directory user matches an existing person, marks that person as a technician and clears its Inactive status.

The wizard does not create a SQL Server login for the account.

Edit a technician account

Select the account and click Edit. The User Account window opens. For a technician account it shows the License group and the Member Of, Effective Permissions, and Workflow Actions tabs.

The Workflow Actions tab lists the step actions and create actions allowed by the account's roles, including actions open to every role.

  • The License group, shown for technician accounts only, holds Named User and Concurrent User; your choice is saved when you click OK. Concurrent User is enabled only while the license has concurrent users. Named User is offered while the active named accounts leave room in the license, or when the account is already saved as named. The window converts no account: an account already saved as named keeps Named User enabled, and an account saved as concurrent stays on Concurrent User, even when that button is disabled, until you pick the other type. A concurrent account that cannot switch to named shows "You cannot change the license type because the limit for the number of named accounts has been reached." An inactive account that cannot be activated shows "You cannot activate this account because the limit for the number of named accounts has been reached." instead.
  • On Member Of, click Add to open Select Roles. It lists every role, including roles the account already has, and you can select several at once; picking a role the account already has adds nothing. The role memberships are saved when you click OK in the User Account window, and the window refuses to save an account without a role.

When the account has an active session and you changed its license type, its status, or its roles, OK saves the account and then shows "Your changes cannot be applied right now because there is an active session for this account. The new settings will be applied to the next session."

Change the login and the person

Use Modify Login in the User Account window:

  1. Choose Windows or Standard or Single Sign-On. The window preselects the type from the current login: a login with a backslash is a Windows login.
  2. Enter the login. Find helps you pick it:
    • For Windows, Find opens the Windows user picker. When you pick an account of the local computer, the computer name is removed from the login, which then has no backslash and is refused for Windows.
    • For Standard or Single Sign-On, Find searches Active Directory and fills in the login from the user's e-mail address.
  3. For Standard or Single Sign-On, select or clear Allow password authentication. The field hint reads "Username for password authentication or email address for SSO".
  4. To attach the account to another person, use the button of the person box. For a technician account, the Select Technician list offers only active persons marked as technicians.
  5. Save your changes.

The login is checked against the type you chose: 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. If you leave password authentication off and the login is not an e-mail address, a warning says the login cannot be used for single sign-on and asks whether to allow password authentication now:

  • Yes selects the check box and takes you to the password field.
  • No saves the account without a password.
  • Cancel keeps you in the window.

Clearing Allow password authentication removes the stored password when you save. An account without a password cannot sign in with a password, through the REST API either.

Set or change the password

In the User Account window, click Change Password and enter the new password in the dialog. The password is checked against the password policy when the policy applies to technician accounts. The command is not available for a Windows login in the DOMAIN\user form.

On an account that has no password and 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 technician and customer

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

  • Convert to SSP warns that all permissions granted through 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. You cannot convert the account you are signed in with: the message "Cannot convert the account that you are currently logged in to." appears.
  • 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, you are offered to mark it: click Yes or Cancel. The conversion goes ahead either way.

Enable or disable accounts

Select the accounts and choose Enable or Disable. If your own account is among them, it is left unchanged, without a message. What disabling does is in Accounts.

The Settings App activates a technician account while the active named accounts leave room in the license, when the account was already active and named at the limit, or when it is a concurrent account. When Enable would take the active named accounts past the license's named users, the Settings App shows an error message that includes "License limit reached."

Delete accounts

  1. Select one or more accounts and click Delete.
  2. Confirm the question: "Are you sure you want to delete the selected item?" for one account, or "Are you sure you want to delete <n> selected items?" for several.

The accounts are then deleted one at a time. 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 what 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." An account is also not deleted when you do not have permission to delete it. 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 a delete of several accounts, the Settings App reports "<n> of <m> items have been deleted."

Deleting an account does not remove a SQL Server login with the same name.