Persons and Groups
On this page
A person record is a directory entry for one person. It holds the person's identity, contact details, place in the organization, and service attributes, but no password or other credential: signing in is done with an account attached to the person. A group is a named set of persons.
Person records
A person record carries:
- Identity: the full name, which is required, first, middle, and last name, title, job title, gender, birthday, and picture.
- Contact details: business, home, and mobile phone, fax, IM address, SMS e-mail, and three lines of address.
- Placement: the organization, the location, and the manager.
- Service attributes: hourly rate, skill level, and work calendar.
- The technician setting.
The technician setting makes a person eligible to be staff. It is off by default, except that a person created through the Technicians list starts with it set. Technician lists and assignment pickers offer only active persons who have it set. In the Web App, a picker that offers technicians is a separate list, not the person list with a filter, and it does not use the person list's columns or views.
Eleven built-in persons represent product components, so that records those components create have a real author: 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. A new database contains these persons and no others. The setting that marks them as built-in is not administrable.
In a new database created with the Default Workflow, persons are created with the create action captioned "Person", through the REST API, and automatically by four actions: from Mail Connector, from Active Directory synchronization, from the Alloy Discovery connector, and from Self Service Portal self-registration.
Groups
A group has a name, which is required, an e-mail address, a manager, and a technicians-only setting, which is on by default. A person can be a member of a group once.
The technicians-only setting decides what a group is for:
- A technicians-only group is a team that tickets are assigned to. The list of assignee groups on a ticket offers only active technicians-only groups.
- A group without the setting collects any persons, technicians or not, for example a department, a company, or customers who get a higher level of service.
A technicians-only group contains only technicians. The product refuses each of these changes:
- Adding a person who is not a technician to a technicians-only group.
- Clearing the technician setting of a person who belongs to a technicians-only group.
- Turning on the technicians-only setting for a group that already has a member who is not a technician.
The rule is enforced in the database, so it holds for the REST API, the Import Wizard, and workflow as well. A group's member count leaves out persons at the inactive status.
Membership has two independent orders: the order of the members inside a group, and the order of the groups in one person's group list. A workflow step that goes through a group's members follows the first order; one that goes through a person's groups follows the second.
A ticket's assignee group is a group. My Tickets lists the open tickets assigned to you or to a group you are a member of; see Tickets.
In a new database created with the Default Workflow:
- Seven groups are supplied. Two of them, Approval Group and VIP Enhanced Service, are not technicians-only, so the Assignee Group list of the ticket action Assign to... does not offer them.
- Assign to... sets a ticket's assignee group and assignee for any technician who may run the action. It does not check whether that technician is the group's manager.
- The manager of a ticket's assignee group is one of the parties escalations can be sent to, as Assignee Group Manager, and can be the approver when approvals are created for the ticket.
- The VIP Enhanced Service group drives two escalations, each set separately for Incidents and for Service Requests. VIP Contact Escalation, which is selected, escalates when a member of the group opens an Incident or a Service Request. VIP Communication Escalation, which is cleared, escalates when communication tasks are run on such a ticket from a member of the group. The escalations go to the party set in VIP Escalation Party, which is Assignee Manager for Incidents. These settings are in Workflow Configuration under Escalation > Incidents and Escalation > Service Requests; see Workflow Configuration and Parameters.
- The two escalations are tied to the supplied VIP Enhanced Service group itself, not to its name. A group you create for your own important customers does not trigger them unless the workflow is changed to use it.
- The configuration also has a service level named VIP Enhanced Service. It is a separate record, not the group.
Persons and accounts
The person is the identity; an account is a credential attached to it. One person may hold several accounts: a technician account and a Self Service Portal account together is the normal case, and nothing prevents more. A login, however, belongs to one account only. Records always refer to persons, never to accounts: an owner, requester, or assignee is a person.
A person's status and an account's state each affect sign-in:
- Saving a person whose status is changed to the inactive status deactivates that person's Self Service Portal accounts. This step does not change technician accounts.
- While a person is at the inactive status, none of their accounts can sign in anywhere, even an account that is still active. The Web App refuses the sign-in.
- Saving the person at an active status again does not reactivate any account.
In a new database created with the Default Workflow, the person's status actions also change the accounts:
- Mark Inactive, in the General group and offered at any status, deactivates every account of the person, technician accounts included, sets the Inactive status, and records "Marked 'Inactive'".
- Mark Active, offered only at the Inactive status, activates every account of the person, sets the Active status, and records "Marked 'Active'".
- A person left at the Disabled status longer than a workflow parameter allows is deactivated automatically, accounts included, as Mark Inactive does.
In the same configuration, the person action Purge Info (hint "Purge
Personal Info", in the Relationships group) anonymizes the person in
place. Its form warns: "This action is not reversible." The action records
"Purged personal information", sets the Inactive status, and deletes all of
the person's accounts, logins, e-mail addresses, and registered devices, and
the audit data of the computers the person owns. It clears the name parts,
title, gender, birthday, job title, the phone and fax numbers, IM address, SMS
e-mail, the three address lines, skill level, hourly rate, manager, and notes,
removes the picture, and sets the full name to Anonymous_ followed by the
person's ID. The organization and location stay.
Active Directory import does not update a person who is at the inactive status. See Active Directory Synchronization.
Creating an account in the Settings App can also change the person record; see Accounts. When the account is created for a directory login, the account wizard either creates a new person from the directory user or updates the person the directory user matches, clearing an inactive status. In both cases, for any account other than a Self Service Portal account, the person gets the technician setting. When the administrator picks an existing person instead, the person record is not changed; for a technician account, the picker lists only active persons who have the technician setting.
In the Web App
Record headers
The header of a person's record shows the full name, with a copy link, and the status. A second row shows the business phone and the primary e-mail address.
The header of a group's record shows the name and the status, over the group's ID. The copy link sits on the ID row.
Person record tabs
A person's record has these tabs: General, Activity, Custom Data, Related Objects, Configuration Items, Allocated Licenses, Tickets, Work Calendar, Notes, History, and Attachments. Work Calendar is the person's personal calendar. The General tab has the sub-tabs Contacts, E-Mail, Logins, Address, Technician, Groups, and Devices.
The Technician sub-tab and the Work Calendar tab are hidden on the record of a person who is not a technician. For allocated software licenses, see License Compliance.
E-mail addresses and logins
The E-Mail and Logins sub-tabs list the person's e-mail addresses and the directory logins the person is known by. A directory login is not a credential.
You add or edit a row in a small dialog, not in the record's own fields:
- The e-mail dialog has a type and an address. The address is required, and an address that does not have the form of an e-mail address fails with "Invalid E-mail address". The dialog's confirm button is unavailable while the save is in progress, and after an attempt that left a field in error.
- The login dialog has a domain and a login. Both are required, and neither is checked for format.
- In both dialogs, Cancel discards the dialog's entries and closes it. On a read-only dialog, the confirm button is hidden.
When the row is saved, the server checks it again and can refuse it even after the dialog's own checks pass:
- An e-mail row is refused with "Email is required." when the address is empty, and with a not-unique message when the address is already in use.
- A login row is refused with "Domain is required.", "Login is required.", or "Login is not unique.".
The uniqueness check on a login row covers the person's own rows with the same domain and login. It is separate from the rule that an account's login belongs to one account only.
You can delete rows from the E-Mail and Logins sub-tabs. A row deleted there, or on the Devices sub-tab, is removed directly: the deletion does not go through workflow.
Set the primary e-mail address or login
One e-mail address and one login can be the person's primary one.
- Open the E-Mail or Logins sub-tab on the person's General tab.
- Select exactly one row. The set-primary button is available only with exactly one row selected.
- Click the set-primary button on the sub-tab's toolbar.
If the person's form has unsaved changes, you choose between:
- Saving the form first. The primary change then runs only after the save succeeds.
- Making the primary change at once, without saving your other changes.
With no unsaved changes, the primary change runs without asking. When the change succeeds, the list and the form reload.
Making a row primary clears the primary flag on the person's other rows of that kind. The person record keeps its own copy of the primary e-mail address and primary login, and the two stay in step: setting the primary e-mail address or login on the person record adds the matching row if it is missing and makes it primary, and deleting the primary row leaves the person with no primary e-mail address or login. A person created with a primary e-mail address gets a matching row of the Business type, and one created with a primary login gets a matching login row, split into domain and login.
Devices
The Devices sub-tab lists the mobile devices registered for push notifications. Registration belongs to the person, not to an account: a person who holds both a technician account and a Self Service Portal account registers a device once, and each row records which of the two mobile apps it is for. The sub-tab offers only a delete button: you cannot open, edit, or re-register a device from it.
Merge duplicate person records
IMPORTANT: Merging person records deletes the source record. Choose the surviving person as the target.
A person record can be merged into another person record from the record's toolbar. The merge drawer offers four ways to treat the target's own values: overwrite only blank values, which is preselected, do not overwrite any values, overwrite all values, or overwrite only non-blank values.
The source's logins are folded into the target: a login whose domain and login the target already has is dropped, and when the target already has a primary login, the source's logins stop being primary. When the target already holds a technician account and the source has the technician setting, the merge turns on the technician setting of the target.
When the merge finishes, the drawer by default opens the target in a new tab; it also refreshes the lists and closes the source record's form.
Group tabs and member order
A group's record has these tabs: General, Activity, Custom Data, Tickets, Related Objects, Notes, History, and Attachments. The Tickets tab lists the tickets assigned to the group.
The list of a group's members has an order dialog on its toolbar. Saving a new order there refreshes the whole form. If the list is not sorted by Rank in ascending order, a notice explains that the displayed order may not match the assigned order. Click Order or sort by Rank to see it. The order of the groups on a person's Groups sub-tab can be changed as well.