CRM Panel/iFrames

Paminga's CRM packages can be used to embed Paminga data directly inside your CRM.

CRM iFrame

Managed Package

If you're using Salesforce, Dynamics, SugarCRM, or SuiteCRM, Paminga's iFrames can be added to Lead, Contact, and Account records as you choose.

The instructions for doing so are specific to each CRM.

Spiro: a Paminga Link on Every Contact

Spiro has no way to embed another app's panel, so Paminga puts a link on each Spiro Contact instead. A rep clicks it and the Contact's Paminga panel opens in a new tab: activity, scores and List membership, the same panel Salesforce and Dynamics show.

Each link is signed for its own Contact and carries no password or token, and your reps never sign in to Paminga. Opening a link signs the browser in as the Panel User for one hour, so anyone holding a link can see what the Panel User can see for that hour. Give the Panel User limited permissions, and rotate the key if a link ends up somewhere it shouldn't.

Set It Up

1. In Spiro, add a Contact field of type Link (Settings › Customizations › Contact). Call it whatever your reps will recognize, for example "Paminga Activity".
2. In Paminga, go to Settings › Integrations › Spiro › CRM iFrame.
3. Under Paminga Link on Spiro Contacts, pick that field as the Spiro Link Field.
4. Pick a Panel User. The panel opens as this user, so create a user just for this and give it limited permissions.
5. Click Save.

Paminga then writes a link to every Contact already synced with Spiro, which takes a few minutes. New Contacts get theirs the first time they sync in either direction.

Turn It Off or Rotate the Key

Every link is signed with a key that belongs to your Spiro integration.

• Rotate Link Key replaces it. Every existing link stops working at once, and Paminga writes new links to every Contact. Do this if a link ends up somewhere it shouldn't.
• Clearing the Spiro Link Field and saving turns links off. Paminga stops writing them, and the ones already in Spiro stop working.

note

If your instance uses IP Restrictions, they apply to these links too: a rep opening a link from an address you don't allow is refused.

Exposing Manually

You can load the Paminga panel into a web browser as you choose. You can:

• Embed via iFrame
• Expose a link that opens a new tab

Panel URL

The panel URL requires two GET variables to function:

• email
• token (for authentication)

https://crm.paminga.com/crm/panel/contact?email=email@domain.com&token=VALID_TOKEN_HERE

If your account is hosted in the EU, load the panel from crm.eu.paminga.com instead, with a token created while signed in at app.eu.paminga.com. A token only authenticates on the instance it was created on, so a US token on the EU host (or the reverse) shows "Unable to authenticate to Paminga".

Use the crm host, not app, on either instance. The panel signs in with the token, and on the app host it would replace the session in your own open Paminga tabs.

URL-encode the email address. A + in an address has to travel as %2B, or the panel reads it as a space and reports that it could not find the contact.

Authentication

The token parameter in the URL is where you have a choice to make:

Create One Token per Salesperson

Creating a distinct Personal Access Token for each sales person is the most secure way to go, but many teams see this as a bit of a hassle.

You have to create and store separate tokens per sales person, pass the correct token as a variable, and manage tokens as personnel changes are made.

Share One Token for All Salespersons

Less secure but more manageable is to create and share a single Personal Access Token across all sales personnel.

The best practice in this case would be to create a user specifically for panel/iFrame authentication and to set restrictive Permissions for that user.

Paminga does not charge you per user, so have no concern about costs.

You could also choose to use an OAuth token, but the net result is the same.