Using External Contacts

You can view external users within the External Contact workspace.

Within the External Contact workspace, click New External Contact. The External Contact form appears.

Enter information into the fields.

--fields--

Field	Description
First Name	The first name of the user.
Last Name	The last name of the user.
Middle Name	The middle name or initial of the user.
Suffix	An optional suffix to add to the name of the user. Select from the drop-down list.
Title	The title of the user. Select from the drop-down list.
Department	The work department of the user. Select from the drop-down list.
Primary Email	(Required) The email address of the user. This field is used in part to verify the user on log in.
Phone1	The primary phone number of the user.
Login ID	The login ID name of the user. This field is used in part to verify the user on log in. If you use internal authentication to log employees in, this identification is also used as the official login ID. If you use internal authentication, the login ID is limited to 30 characters. If the employee is using NT authentication, the limit does not apply. A login ID should be meaningful, such as a role in the system (Admin) or a first initial/last name (CTracker).
Phone2	The secondary phone number of the user.
Enable Internal Auth	Performs login authentication for this employee. If selected, internal authentication is available for the employee. Otherwise, it is disabled. Local authentication requires employees to enter an application-specific login ID and password when accessing the application. Enter a password for the login, then reenter the password to confirm; the ID automatically fills from the login ID defined previously. LDAP authentication verifies employee login information for employees imported using the LDAP Active DirectoryMicrosoft's Active Directory is a service that stores and manages network-based entities such as applications, files, printers, and people. integration. Employees enter their Active DirectoryMicrosoft's Active Directory is a service that stores and manages network-based entities such as applications, files, printers, and people. employee name ([domain name]/[employee ID]) and password to log on to . To use LDAP authentication, you must specify the LDAP server path to authenticate against as well as the employee name and password required to access that server (if applicable); specify this information in the LDAPInfo.xml configuration file located in the messaging folder of your application installation directory.
Enable External Auth	Enables the user to access the application using OS authentication. Authentication is supported via Open ID, SAML/ADFS, and LDAP, which allows users to access the application from another website.
Disabled	Disables the ability of the user to log in. Their information still appears in the user list.
Disable Password Expiration	Overrides the password expiration setting specified by the administrator.
Organizational Unit	(Required) The organization unit associated with the user.
Team	(Required) The team associated with the user. Select from the drop-down list.
VIP	Designates this user as a VIP.
Internal Auth Passwd	The password the user uses to access the application using the internal login ID.
Login for External Auth	The external login ID. Enter a unique ID. Used if the user is authorized to login from outside the organization. This value is allowed to be null (empty), but if used, the value must be unique. You can employ multiple external authentication providers. Click Add New, then provide the login for the user and select a new authentication provider. In some cases (for example, Google), this may be a profile URL. This field is populated the first time that the user logs in using the external authentication. Users cannot use the same external account for authorization purposes.
Is Named User	Designates the user as a named userA user flagged as a named user. After a user is flagged as a named user, a named user license is consumed, whether the user is logged in or not.. Tracks named user licenses.
Is Auto Provisioned	Designates the user as auto provisioned. When an employee first logs into the application using an authentication provider URL, then a new employee record is created and this option shows selected. To add new users via authentication, you must select the auto provisioning option in the authentication provider record. You also have the options to auto provision the role, status, and team of the new user.
Creation Method	The creation method. Choose from the drop-down list: Auto Provisioned through OpenID Auto Provisioned through SAML Created by Email Listener Created by LDAP Import Manually created The first two methods of creation are populated automatically if the user is created via auto provisioning. The authentication method depends on the identity provider protocol. For the created by email listener method, the employee record is created when the user sends an incoming email. The option to create or link to an employee must be selected for the business object, referenced in the incoming email, in the Inbox settings of the tenant email configuration record. If the employee record is created when the user is imported via LDAP, then the record is created via LDAP import.
Location	The work location. Select from the drop-down list.
Primary Address	The primary street address of the user.
City	The primary mailing city of the user.
State	The mailing state of the user.
Country	The primary mailing country of the user.
Zip	The mailing zip code of the user.

Click Save

from the toolbar.