InterAction relies on a list of valid user accounts when determining who can log onto the system and access information throughout InterAction.
InterAction also uses this user information for other features, such as when tracking who edited a particular record in the audit trail, adding relationships that indicate the user knows a contact, adding activities, and “tying” each user to his or her user contact list.
You can import multiple users from a comma separated values (CSV) file or create them one at a time.
Security and Proxies
Typically, secretaries or administrative assistants help professionals to maintain contact information. In InterAction, users can have proxies, or users that have access to the user’s contact data in InterAction and can perform actions on behalf of the user. For example, a secretary can add a contact to a mailing list and set the professional as the contact’s sponsor, a secretary can add an activity and set the professional as the originator of the activity, or the secretary can manage a professional’s contacts.
Users can, however, maintain Private contacts in their user contact lists that cannot be seen by the proxy.
For more information on setting a proxy for a user, see Managing User Proxies.
Administrative Users and Groups
To perform some InterAction features, you must be logged in as a special user or be a member of a special group. For example, the System Administrator Account (IAAdmin) is used for many special situations, such as initializing the database, configuring the audit trail, and creating other system information.
For more information about special users and groups, see Administrative Users and Groups.
Groups
Groups are used to simplify the process of setting options for several similar contacts at the same time. For example, you can give permissions, set access rights, or set the visibility for an activity to just a specific group of users. Some groups are provided with InterAction, however, you should create your own groups to match the logical groups at your organization. For more information, see User Groups.
Components of a User
Review the following table to identify the information included in a user account.
| Item | Description |
|---|---|
| General | |
| Account Name |
When selecting account names, use names that match account names in other systems, such as network account names. This reduces the number of different account names users need to remember. Using account names that match users’ network account names lets you use the network user authentication instead of requiring users to enter their account names and passwords. See Setting User Account Authentication for the Web Client and Selecting User Validation Options for the Windows Client for more information. |
| First Name/Last Name | (First and Last). This is normally the user’s name. This name appears in many places in the system, such as in fields showing the last person to edit information. |
| Password | To maintain security, the password is stored in encrypted format in the database. |
| Grace Logins | This is the number of times a user can log on using an expired password. This is only used in the Windows Client. The Web client ignores password expiration and grace logins for users. |
| Professional | This is used when generating usage statistics. It can also be used to filter user additional fields. |
| Prevent Access to Windows Client | Select this option to prevent the user from accessing the Windows Client. The user will only have access to the Web Client. |
| Account is disabled (inactive) |
A user can either be active or inactive.
Setting the status of an existing user to Inactive does not change any existing fields that contain the name. For example, if you change user “EMROBERTS” to Inactive, his name still appears in the “Last Edited” field of any records for which Ed Roberts is the last editor. The number of active users you can create is limited by the number of licenses your organization has purchased. See Licensing InterAction Users for more information. |
| Contact Record |
This is a corresponding contact that represents the user in InterAction, normally linked into the Our Personnel folder. A user must have a Contact Record set before he or she is allowed to log on to InterAction Web Client, Desktop Integration, or COM API, or use LexisNexis InterAction for Microsoft® Outlook® (IMO). |
| Contact List | Each user has a user contact list that contains contacts of interest to the user. These contacts can be in the user’s list only or be connected to contacts in the firm’s list. Contacts located in a user’s contact list are called user contacts. When you create a user, that user’s contact list is automatically created. For more information about User Contact Lists, see “What Are User Contact Lists?” on page 106. |
| Groups | |
| Member of |
This indicates the group membership of the applicable user. Add or remove the user from groups as applicable. Groups are used for assigning access rights and permissions to features like duplicate merge and the data quality tools, sharing searches in the Windows Client, and setting visibility for activities. Maintaining a large number of user groups may be confusing to end users and generate maintenance work for administrators. For more information about Groups, see “User Groups,” starting on page 164. |
| Proxies | |
| Has as a proxy | Each user may have one or more users assigned as proxies. For more information, see “Managing User Proxies” on page 160. |
| Is a proxy for | Each user may be a proxy for one or more users. For more information see “Managing User Proxies” on page 160. |
| Regional Settings | |
| Language | Specify the language that the user speaks. In conjunction with the Country setting, this forms the user’s regional settings and affects how times, dates, numbers, and measurements appear throughout InterAction. |
| Country | Specify the country where the user resides. In conjunction with the Language setting, this forms the user’s regional settings and affects how times, dates, numbers, and measurements appear throughout InterAction. |
| Reminder Settings | |
| Can create reminders and receive reminder messages |
If your organization has the reminders feature enabled, select this check box to allow the user to use reminders. For more information on the reminder settings available, see the Configuring InterAction guide. |
| Other | |
| IQ Calculated Relationship Strength | For more information on hiding InterAction IQ 2.x calculated relationship strengths, see the InterAction IQ 2.x User Guide. |
| Default Document Repository |
When a user adds a document to InterAction, the document is stored in a document repository. Since users are not exposed to document repositories, you choose a repository for them. You only need to assign repositories to users if your environment includes multiple repositories. |