Administration Guide

Accounts

On this page

An account is what lets someone sign in to Alloy Navigator. The identity itself is the person record: the name, the organization, and the contact details live there. The account is a credential attached to a person: a login, a password where one is used, the account type, and whether the account is active. An account does not repeat any of the person's details.

Every sign-in resolves to an active account whose login matches. The one exception is accountless sign-in to the Self Service Portal: when a single sign-on provider or a directory is marked as accountless in the portal's settings, a user it identifies who has no matching account is let in. For single sign-on, the portal matches the asserted e-mail address against existing persons and, if none matches, creates a person from the asserted full name and e-mail address; a directory user is imported as a person on first sign-in. The session then runs against that person. How each sign-in method works is described in Authentication Methods.

Administrators manage accounts in the Admin Center and in the Settings App. For how the two applications relate, see Admin Center and Settings App.

Account types

Type Used by Signs in to Signs in with
Technician Technicians Web App (and the Admin Center from it), Settings App, Self Service Portal, Alloy Navigator mobile app, REST API A password, Windows or directory credentials, or single sign-on
SSP customer End users of the Self Service Portal Self Service Portal and the Alloy Self-Service mobile app A password, Windows or directory credentials, or single sign-on
API application Integrations that call the REST API REST API An application ID and a secret
Service Background components of the product Never signs in Nothing

In the Settings App, a technician signs in with a password or with Windows credentials only: directory credentials and single sign-on are not accepted there.

Technician accounts

A technician account carries a license type:

  • Named: the license's Named Users value limits how many active named technician accounts can exist.
  • Concurrent: the license's Concurrent Users value limits how many technicians with concurrent accounts can be signed in at the same time. The number of concurrent accounts is not limited. A technician signed in to two applications at once takes at most one concurrent seat.

What a technician may see and do is set by the security roles the account is a member of; see Security Roles. A technician account cannot be saved without at least one role.

A technician account can sign in only while the account is active and belongs to a person whose status is not Inactive. To sign in to the Web App or the Settings App, the account must also have a Named or Concurrent license type.

In the Admin Center, the accounts list shows an Authentication Type for each account. It is worked out from the login and the password, not stored: Windows for a login that contains a backslash, SSO for an account without a password, and Standard otherwise.

To create and edit technician accounts, see Create and Maintain Technician Accounts.

Customer accounts

An SSP customer account signs in to the Self Service Portal and the Alloy Self-Service mobile app. It does not use a license seat, and security roles do not apply to it. Instead, its access level decides whose tickets and service requests the customer sees in addition to their own:

Access level The customer also sees the tickets and service requests of
Regular User Nobody else: only their own
Manager People who report to them
Group Manager Members of their groups
Department Manager People from their organization
Organization Manager People from their organization and its sub-organizations

An administrator creates customer accounts in the Admin Center or in the Settings App, and end users can register themselves in the portal; see Create and Maintain Customer Accounts. In the Web App, a technician can also create, edit, and delete a person's customer accounts and set their passwords. There, a login must not be empty and must not already be in use, whatever its letter case, and a password is checked against the password policy.

Self-registration creates the person first and the account second; when the portal requires registrations to be authorized, nothing is created until the registration is approved. The portal rejects a registration when the submitted e-mail address is already the primary e-mail address of a person, or when the login already belongs to an account or to a pending registration.

Accounts that are not people

  • API applications. An API application is an account together with a service person that carries the application's name. Its application ID and secret are generated for you, and the secret is kept as generated, so anyone who can open the application can read it. Security roles do not restrict an API application: its sessions run as service sessions. Applications are managed on their own list in the Admin Center and in the Settings App; see API Applications.
  • Service accounts. Background components do not sign in; they identify themselves to the database, and the records they create are attributed to built-in service persons. A new database holds eleven of them: Automation Server, Active Directory Integration, Alloy Discovery Integration, AlloyScan, Archiving, Mail Connector, Scheduled Reports, Self Service Portal, Import Wizard, Alloy Navigator API, and Scheduled Task Agent. The flag that marks them as service persons is hidden on the person form and is not administrable.
  • The reserved support account. One account is reserved for the product's own use. It is not shown in account lists and does not count against the named technician limit. No other account can take over its login.

How accounts relate to persons

  • One person, several accounts. A person can hold more than one account. The usual shape is one technician account and one customer account for the same person. A login, however, belongs to one account only: no two accounts can share it.
  • Records point to persons. Requesters, owners, and assignees in records are always persons, never accounts. What a technician creates is attributed to the technician's person.
  • Mobile devices belong to the person. A device registered for push notifications is registered for the person, once per mobile app, whichever account signed in.
  • The person's status affects the accounts. When a person record is saved with its status changed to Inactive, that person's customer accounts are disabled. Technician accounts are left as they are. While the person is Inactive, none of the person's accounts can sign in anywhere, even an account that is still active. Saving the person with an active status again does not re-enable any account.
  • Creating an account for a directory login can change the person. When the Settings App's account wizard is given a DOMAIN\user login, it either creates a new person from the directory user or, for the existing person the directory user matches, clears an Inactive status. For any account other than a customer account, the person is also marked as a technician. When you pick the person instead, nothing on the person is changed. See Create and Maintain Technician Accounts and Create and Maintain Customer Accounts.
  • The account type can change. An account can be converted from technician to SSP customer and back; see Create and Maintain Technician Accounts.

For the person records themselves, see Persons and Groups.

Disable an account

Disabling an account changes only whether the account is active, and its next sign-in is refused. It does not end sessions that are already open: to end them, terminate them in the Admin Center as described below.

In the Web App, a refused sign-in names the login:

  • For a typed user name and password that fails both the account check and the directory check: "Sign-in failed for user '<login>'."
  • For Windows authentication or single sign-on: "Your account '<login>' is not an active Alloy Navigator account. Please contact your Alloy Navigator administrator."

The Web App also looks the account up again when it reopens the database connection of an open session, and then refuses a disabled account with the second message.

In the Settings App, the sign-in dialog refuses a disabled account with a message that names the login.

To disable an API application, see API Applications.

In the Admin Center

To disable or enable one account:

  1. Open the account.
  2. On the General tab, click Make Inactive, or Make Active to enable an inactive account.
  3. Save the account.

The Make Active / Make Inactive button is not shown on your own account, so you cannot make your own account inactive from this tab.

The Admin Center refuses to save an active technician account, and shows its general error message, if the account is named and the active named accounts would exceed the license's Named Users value, or if the license value for the account's license type (Named Users or Concurrent Users) is 0.

To disable or enable several accounts at once, select them in the accounts list and use the bulk disable or bulk enable action:

  • If the selection includes your own account, an error message appears. Click OK: your account is removed from the selection and the others are disabled. The same message also appears when your own account cannot be found in the loaded list; then no account is removed from the selection.
  • Before enabling, the Admin Center checks that the license has enough free named seats for the inactive named technician accounts in the selection. If it does not, a message appears and no account is enabled.

To end the open sessions of a disabled user:

  1. Open the User Sessions page.
  2. In the Logged Users panel, select one or more sessions.
  3. Click Terminate. At "Are you sure you want to terminate the selected session?", click Yes.

In the Settings App

  1. Go to Users & Security > Accounts and Roles > Accounts.
  2. Select one or more accounts.
  3. Right-click the selection and choose Disable, or Enable.

Your own account is skipped without a message when it is part of the selection. If enabling would take the number of active named technician accounts past the license's Named Users value, the Settings App shows the license-limit message, which contains "License limit reached."