Skip to content

Installation Instructions



This is your checklist during the installation.

  1. Create Userlike account.
  2. Add limepkg-userlike as a dependency to your solution.
  3. Build and deploy your solution.
  4. In Lime Admin, go to the Setup page in Lime Chat's settings and follow the instructions.
    • Create an instance for each limetype the installation should target. Choose whether media files should be imported as documents, and if so, configure the document limetype.
  5. Configure the add-on.
  6. Configure in LISA.
  7. Configure Userlike.
  8. Configure Desktop Client.

Userlike Account

Start with creating a free trial account from Userlike's homepage.

Use the format:

Sign-up Sheet Name Value
First name Lime
Last name Admin
Email address userlike\<customername>
Password Generate from Keeper

After you have created the trial account. Notify Userlike by filling in this form. Userike will change the account from a trial account into the correct type based on input values. If you can't get past this step, contact


Descriptives and Icons (If Lime CRM Desktop Client)

  1. Add the descriptive expression found in legacy/lip/lisa/descriptives/ulconversation.txt to the ulconversation table.
  2. Add the icon found in legacy/lip/lisa/icons/userlike.ico to the ulconversation table.

Additional Data Structure

  1. Make sure the length of the note field on the history limetype is set to max (set length to 0). The history note will be truncated with ... if the chat transcript doesn't fit.


  1. Create one new table specific policy called tbl_conversation and apply that policy on the conversation table.
  2. Set the following privileges for the groups that should be able to use Lime Chat in Lime CRM:

    Policy name R W A D Apply to
    tbl_conversation conversation table


    Using Lime Chat in Lime CRM means that the user can manage conversations in Lime CRM. For example, connect a new conversation to a limeobject that already exists.

API User

Go to policies and set the correct privileges for the (System) Userlike integration group on each table policy. This is an example of common settings:

| Read | Write | Add | Delete | Apply to |
| • | • | • | | Conversation table |
| • | • | • | | History table |
| • | • | • | | ALL tables that are configured as instance limetypes. Typically: helpdesk, deal |
| • | • | • | | Document table - if you want to import media files as documents in Lime CRM |
| • | • | | | Person table - if you want to attach the identified person to the created instance limeobject and to the created history notes |
| • | • | | | Coworker table - if you want to attach the identified coworker to the created instance limeobject and to the created history notes |
| • | • | | | Company table - if you want to attach the identified person's company to the instance limeobject and to the created history notes |


Configure Userlike according to these instructions.

  • Enter this as the Lime CRM URL: <SERVER_URL>/<APP_NAME>/limepkg-userlike/userlike/.
  • From the installation report copy the generated API key for the newly created userlike@lime user and use it as token.

Desktop Client

The desktop app uses the same configuration as the web client but the following steps are required to enable the desktop version.

  1. Add VBA module AO_Userlike.
  2. Add LBS apps addon_userlike to your Actionpad apps folder.
  3. Use the following example in your GeneralExplorerHandler to hijack the new conversation command in Lime CRM (adjust ulconversation if you are using another limetype):
    Private Sub m_Explorer_BeforeCommand(ByVal Command As CommandEnum, ByVal Parameter As Variant, Cancel As Boolean)
        On Error GoTo ErrorHandler
        If Not m_Explorer is Nothing Then
            If m_Explorer.Class.Name = "ulconversation" Then
                If Command = lkCommandNew Then
                    Cancel = True
                    Call AO_Userlike.OpenDialog
                End If
            End If
        End If
        Exit Sub
        Call LC_UI.ShowError("GeneralExplorerHandler.m_Explorer_BeforeCommand")
    End Sub


You might need to enable that VBA events are caught also for explorers on inspectors if you are running an old Lime Base, read more here.