# Non-Corporate Contacts

## Description

Non-corporate contacts are external directory entries, such as material or equipment suppliers that are listed in the MiCollab Client corporate directory. They are not MiCollab system users, and as such, are not assigned with MiCollab application services, and are not listed in the User and Services application directory. Non-corporate contacts are typically configured only with a name, external phone number, and an e-mail address. This type of contact does not have an associated login ID or password and does not consume licenses on the system.

You can assign entries in the Active Directory database as non-corporate contacts and IDS will automatically update the MiCollab Client Corporate Directory with them during the next synchronization event. During the IDS synchronization, the system applies the default "Contact" role and the associated default " MiCollab Client " template to the non-corporate entries. When users start up their MiCollab clients, the system updates the user's Contacts list. Users can then place calls to the non-corporate contacts using "click to call" functionality from their phone clients.

Users and non-corporate contacts that are obtained from the directory service via IDS are organized into groups in the MiCollab Client Enterprise corporate directory based on the Distinguished Name attribute. The Organizational Unit (OU) information in the Distinguished Name attribute defines the group names in the MiCollab Client corporate directory. Non-corporate contacts that are assigned to an Organizational Unit in Active Directory are inserted into a corresponding group in the MiCollab Client corporate directory. Below are examples of Distinguished Names for three non-corporate contacts:

cn=acme heating and cooling, ou=maintenance, dc=maslab, dc=local

cn=vista paper products ltd, ou=suppliers, dc=maslab, dc=local

cn=jy office supplies, ou=suppliers, dc=maslab, dc=local

## Conditions

- To support this functionality MiCollab Client must be configured in Integrated Mode.

- By default, MiCollab Release 6.0 SP1 and later systems are configured to synchronize with the users and non-corporate contacts that are contained in the Active Directory database.

- Prior to MiCollab Release 6.0 SP1 only user contacts were synchronized. If you upgrade a pre-Release 6.0 SP1 system to Release 6.0 SP1 or later, you must manually configure the system to synchronize non-corporate contacts.

- The following directory service fields are not imported via MiCollab IDS: Middle name, Address, City, State/Province, ZIP/Postal code, and Display picture.

- A maximum of three phone numbers are supported per non-corporate contact in MiCollab Client .

- Users that you create manually from the USP Add or Quick Add forms are not configured with a Distinguished Name and therefore are not listed in a contact group. Instead, they are listed in the top level of the MiCollab Client corporate directory.

- You cannot import non-corporate contacts via a CSV or LDIF file from the Bulk User Provisioning tool.

- Non-corporate contacts that are synchronized from the directory service are displayed as read-only in the Bulk User Provisioning tool.

- The Manage Detained Queue in the Bulk User Provisioning tool lists any non-corporate contacts that have been detained or have failed. The Role field displays "Contact" for non-corporate contacts..

- The default "Contact" role and template are not included in the User Template or User Role lists of USP and you cannot apply the default "Contact" role to a user from the USP Quick Add form. The default Contact role and template are only applied to contacts imported from Active Directory.

- Contacts are not shared with MiVoice Business database even if Single Point Provisioning is enabled.

## Define the Non-Corporate Contacts on Active Directory

You can specify Active Directory entries as MiCollab Client non-corporate contacts using either of the following methods:

## Create a Non-Corporate Contact

To create a non-corporate contact on Active Directory:

1. Log into Active Directory as administrator.

2. Click Start > Active Directory Users and Computers.

3. Select the Organizational Unit (OU) for the contacts.

4. Right-click and select New > Contact.

5. Complete the Contact fields. When the databases are synchronized, MiCollab IDS adds the directory entry as a non-corporate contact.

## Change an Existing Active Directory Entry to a Non-Corporate Contact

To change an Active Directory user entry to a non-corporate contact.

1. Log into Active Directory as administrator.

2. Click Start > ADSI Edit. The ADSI Edit window opens.

3. Open the Organizational Unit (OU) of the users.

4. Select the user.

5. Right-click and select Properties. The user's Properties window is displayed.

6. On the Attribute Editor tab, set the "employeeType" attribute to "Contact". By default, MiCollab maps the "employeeType" attribute to the "Role" attribute.

7. When the databases are synchronized, MiCollab IDS changes the entry into a non-corporate contact.

## Configure MiCollab IDS to Synchronize User Entries and/or Non-Corporate Contacts

By default MiCollab IDS synchronizes the user entries and non-corporate contacts in the directory service database with the MiCollab Client corporate directory. You can configure MiCollab IDS to synchronize only users, only non-corporate contacts, or both users and non-corporate contacts:

1. Log into the MiCollab server manager.

2. Under Configuration, click Integrated Directory Service.

3. Under Actions, click Edit .

4. Set the Default query string field:

   To import | Set Default Query String field to . . . | Result
   --- | --- | ---
   Users and contacts (default) | |(ObjectClass=user)(ObjectClass=contact) | Directory service entries with object Class set to "user" are added to the USP and MiCollab Client directories as user entries; Directory service entries with Object Class set to "contact" are added to the MiCollab Client directory as non-corporate contacts.
   Users only | (ObjectClass=user) | Directory service entries with object Class set to "user" are added to the USP and MiCollab Client directories as user entries.
   Contacts only | (ObjectClass=contact) | Directory service entries with object Class set to "contact" are added to the MiCollab Client directory as non-corporate contacts.

5. Click Save.

6. Perform a Full IDS Synchronization. Ensure that the Re-initialize on next cycle box is checked when you perform the sync. If you perform a the sync with this box unchecked, your existing contacts will not be listed in the MiCollab Client corporate directory.

↑