Contacts

Managing a contact list is easy for Staff and Company Administrators, or you can empower your users to self-manage their group memberships. To do this, simply enable the feature which permits automatic additions to the list when users join a group or organization.

In the Staff site, go to Settings > Contacts > General.

Determines the system default country. The drop-down is a list of hundreds of available countries to select from. 

  • When selected:
    • All users, including Public users, are able to add themselves directly to groups without approval from an administrator.
  • When not selected:
    • Public users are able to enter an organization during registration, but this does not add them to the organization group or organization roster.
    • Company administrators can add contacts to the list for the organization (or group) they moderate or administer.
    • Staff users (Full, Casual, or with administrative privileges) can add contacts to groups or organizations.

A Company Administrator can bill to their organization; however, you can extend that functionality to all users, if desired.

  • Company administrators only is set by default. If this option is selected, only a Company Administrator or Staff user acting On Behalf Of a user can select their organization as the Bill To contact.
  • All users enables all users, including public users, the ability to select their organization as the Bill To contact. When this option is selected, the Bill To payment detail in the cart will default to Myself with the organization also listed as an option.
  • All users - organization selected by default allows all users to select their organization as the Bill To contact. When this option is selected, the Bill To payment detail in the cart will default to the user’s organization with Myself also listed as an option.

Warning!  

Do not allow all users to link to an organization if you also allow users to bill an organization. This would allow anyone to create an account and link and bill to any organization.

The regular expression rule is used to determine if the email address a user enters contains valid characters as specified in the regular expression syntax. You can modify the regular expression to specify your own rule. The default regular expression, \w+([-+!$%&*/=?{|}.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*, allows email addresses to contain specific characters.

  • A "word character" is any alphabet or numeric characters and includes underscores (_).
  • The email address must begin with a word or numeric character, or an underscore, any of which can be entered one or more times.
  • Specific special characters (- -+!$%&*/=?{|}.' -) are allowed if they are followed by at least one word character. Special characters are not required.
  • The at sign (@) is required.
  • Word characters are allowed, but not required.
  • Hyphen (-) and period (.) are allowed after the “@”. If they are used, they must be followed by word characters.
  • The period (.) is required.

Note: This default expression does not allow foreign characters.

  • niceandsimple@example.com
  • very.common@example.com
  • a.little.lengthy.but.fine@dept.example.com
  • disposable.style.email.with+symbol@example.com
  • other.email-with-dash@example.com
  • user@[IPv6:2001:db8:1ff::a0b:dbd0]
  • "much.more unusual"@example.com
  • "very.unusual.@.unusual.com"@example.com
  • üñîçøðé@example.com
  • üñîçøðé@üñîçøðé.com

In the Staff site, go to Settings > Contacts > Contact security.

These system settings allow for granular security settings when viewing contact records. This is accomplished by providing separate security settings for three different user types in iMIS. These settings provide system-wide permission to view the public profile information of other users.

When making changes to these user access queries, it is vital that you update the search index for your updates to take effect. For more information on rebuilding your search index, please see Deleting community posts and rebuilding the search index.

For example:

  • AllUsersAccessQuery returns only contact A.
  • AuthenticatedUsersAccessQuery returns only contact B. 
  • MemberAccessQuery returns only contact C.

Note: When creating or editing an Online User Access query, you must use the NetContact business object and have Contact Key and iMIS ID properties in the display tab. It is recommended to have an iMIS ID property in the filters tab as well. iMIS provides example queries that you can copy and adjust to fit your organization's needs:
— $/Samples/Security/UserAccess/Contacts available to all users
— $/Samples/Security/UserAccess/Contacts available to members

Visitors to your site might receive an error if they click on the name link of a contact they don’t have permission to view. If your customers report seeing these messages frequently, you may want to review your queries in these fields to loosen the restrictions.

Note: After you select a query to determine your online user access, you can edit it directly from this page by clicking Edit source query.

Create or edit a query for this field to determine which contacts' public profiles are visible to visitors who have not logged in.

Warning!  

If this field is left blank, visitors will not be able to see the public profiles of any of your iMIS contacts and an error message will be displayed.

Create or edit a query for this field to determine which public profiles all logged-in users can view.

Logged-in users will not be able to access public profiles or information for any contacts not included in this query. For example, they will not be able to register contacts for events using Register Someone Else if the contact is not in this query.

Warning!  

If this field is left blank, logged-in non-members will effectively have the same level of access as unauthenticated users.

Warning!  

If this field is left blank, members will effectively have the same level of access as logged-in non-member user.

Create or edit a query for this field to determine which public profiles members of your organization are allowed to view.

The account management settings allow you to tailor the account notification messages that display when an account is created, a password is changed, or a sign-in attempt fails. You can also set the address from which email notifications of password resets and username requests are sent and the text contained in those emails.

In the Staff site, go to Settings > Contacts > Account management.

Specifies the message that is displayed when an account is created or a password is changed. The default message is “The password must be at least {0} characters long and contain both letters and numbers.” Two variables can be added to the message: {0} or {1}. The {0} variable refers to the minimum password length allowed and the {1} variable refers to the minimum non-alphanumeric characters allowed.

The values for these variables are set in the web.config file in the CustomizedProvider line. The default for the variable {0} is 7 (minRequiredPasswordLength), which is the minimum length required for PCI compliance. The default for the variable {1} is 0 (minRequiredNonalphanumericCharcters). Non-alphanumeric characters are not necessary for PCI compliance, so setting a minimum value for variable {1} is optional. However, requiring non-alphanumeric characters increases password security.

Specifies the message that is displayed when a sign-in attempt fails. The default message is “The username or password you entered is incorrect.” If you would like to change this message, edit the Contact Sign In content item directly.

Enter the email address where email notifications will be sent.

The LogonInformationRequestMessage is sent to users who have submitted the Forgot my username form. The default message is “<p>We received a request for the username associated with this email address. Based on the information provided, your username is:</p><p>[UserId]</p><p>Please click the link below to return to our website and sign in:</p><p>[LogonUrl]</p><p>If clicking the link does not work, you can copy and paste it into your browser's address window.</p>.”

The PasswordResetRequestMessage is sent to users who have submitted the Forgot my password form. The default message is “<p>Password reset request for username <b>[UserId]</b></p><p>We received a request to reset the password for the username referenced above. If you made this request, please click the link shown below to reset your password.</p><p>If you did not request to have your password reset, you can safely ignore this email.</p>Please click the link below to reset your password:</p><p>[LogonUrl]</p><p>If clicking on the link does not work, you can copy and paste the link into your browser's address window.</p>.”

You can use the following variables in the LogonInformationRequestMessage and the PasswordResetRequestMessage. When an email is sent, the variables are replaced with the appropriate values.

  • [UserId]
  • [ContactId]
  • [Email]
  • [LogonUrl]

Use HTML or CSS to modify the display of the emails.

  • HTML and inline styles work best in emails, because some email clients ignore externally linked CSS files. For example, the following inline style turns the header text blue and changes the font:

<h1 style="color:#0000FF;font-family:Georgia,serif;">Heading text</h1>

  • Use full paths to images, not relative paths. For example:

<img src="http://www.servername.com/images/logo.gif" alt="Company logo" />

  • Test your email messages in different email clients to make sure everything looks the way you want.

Staff users can configure the types of communications that can be sent by your organization. This enables you to enforce the preferences of members who do not want to receive certain types of communications.

In the Staff site, go to Settings > Contacts > Communication preferences. You can add a new communication type or edit a selected communication type.

To add a new communication type:

  1. Click Add new.
  2. Enter the name of the new communication type.
  3. (optional) Provide a description of the communication type.
  4. Define the default subscription properties of the communication type:
    • Subscribe by default (Opt-out) — Users will receive communications until they choose explicitly to no longer receive communications.
    • Users must subscribe (Opt-in) — Users will not receive communications unless they subscribe.
  1. Select the status of the communication type:
    • Active — the subscription properties for the communication type are applied.
    • Inactive — the subscription properties for the communication type are not applied. The inactive communication status cannot be assigned to communication templates or documents.
  1. Save.

Note: System-defined communication types (Primary, Shipping, and Billing) cannot be edited.

In the Staff site, go to Settings > Contacts > Social media to integrate your websites with a social medial network.

  1. In the Staff site, go to Settings > Contacts > Social media.
  2. In the Authorization Providers table, add a new provider.
    • Specify the Provider.
    • Enter the App Id and App Secret you received from the Provider when you created your app. See Creating an Authorization Provider App for more information.
    • Enable the provider to display a button in the Contact Sign In content item that allows website users to sign in with a social media account from the provider. Enabling a provider also allows:
      • You to configure any Contact Account Creator on your site to allow users to sign up with a social media account.
      • Users, when updating their profile photo in the Contact Profile Picture content item, to use their Facebook or LinkedIn profile photo on your website.
  3. (optional) To prompt users to link their social media and iMIS accounts the first time they attempt to sign in with a social media account, confirm that Prompt to link social media account to an existing or new iMIS account is selected. An additional window displays the first time users sign in with a social media account, prompting them to enter their iMIS username and password. A user can also choose to use their Facebook or LinkedIn profile photo as their profile photo on your website during the linking process.

    4. Note: If you do not prompt users to link their social media and iMIS accounts, a new contact is created and linked. Since users do not see a visual prompt to link to an existing iMIS account, there is an increased chance for creating duplicate contacts when users use different email addresses for the social media and iMIS accounts. However, if a user uses their Facebook or LinkedIn email with their iMIS account, they will still be prompted to link to the existing account instead of creating a new account.

    • (optional) If you prompt users to link their social media and iMIS accounts, you can tailor the HTML for prompt or use the default message.
  4. (optional) If you want users who choose to link to a new iMIS account to enter additional contact information in a Contact Account Creator content item, select Prompt for new contact information when creating an account with social media.

  5. Note: When you prompt users to enter new contact information when creating an account with social media, users are directed to the content at the CreateAccountSocialMedia shortcut. This content contains a Contact Account Creator out-of-the box, but it can be modified. The Contact Account Creator in this content, however, must always be configured to include an option to create an account.

For more information, see Using social media to log in.

To obtain an App Id and an App Secret from Facebook, complete the following steps:

  1. Register as a Facebook developer.
  2. Create a new app.
  3. Enter the requested information and create the app.
  4. In the Basic Settings, add a website platform, enter the URL for your website, and save.
    • An App ID and App Secret are automatically assigned. You will need to enter these items as Social Media Settings in the iMIS Staff site.
  1. In the Advanced Settings, enable Client OAuth Login and save.
  2. In the App Details, enable Website as a listed platform, configure the App Center for emailand user_location as permissions, and save.
  3. In Roles, add test users and save.

    Note: You need test users because regular Facebook users cannot use your app until it is officially live.

You can find your App Id and App Secret in the dashboard or basic settings.

To obtain an App Id (Client ID) and an App Secret (Client Secret) from LinkedIn, complete the following steps:

  1. Register as a LinkedIn developer.
  2. Create a new app.
  3. A Client ID and Client Secret are automatically assigned. You will need to enter these items as Social Media Settings in the iMIS Staff site.

    4. Note: The Client ID is the App Id and the Client Secret is the App Secret in iMIS.

  4. Enter the Authorized Redirect URLs for all iMIS websites that would like to sign in with LinkedIn.
  5. From the Staff site, go to Manage websites, select your website, and copy the Secure URL(s) pointing to the IIS website root.
  6. Paste the Secure URL(s) pointing to the IIS website root to the Authorized Redirect URL in LinkedIn.
  7. You must add /sign-linkedin to the Authorized Redirect URL.

    8. Example:  

    www.mydomainname.com/sign-linkedin

  8. In the Settings, complete all of the required fields.