See more

Steps to migrate to the new Blend-Encompass integration 

Avatar
Indya
  • Updated
Follow

Please contact support@blend.com if you’d like to walk-through your set up in Encompass

 

In order for lenders to take advantage of Blend’s new Blend-Encompass integration, user administrators at the lender will need to create an API user in their Ecompass instance. This will act as interface between Blend and their Encompass instance 

 

See below for step-by-step instructions on the process.

Step 1: Blend provides lender an API Client ID that lender administrator will use when creating a user

Your Blend point of contact will provide you a client_id (or API Client ID). This is part of an authentication protocol that Ellie Mae has issued Blend in order to access Ellie Mae’s APIs on your behalf. 

Example: client_id = rmsgpbp

Step 2: Navigate to Settings > Organization/Users in Encompass

 image-20200427-184913.png

image-20200427-184945.png

Step 3: Click the green plus icon to create a new user

image-20200427-185147.png

Step 4: Enters user details

Click the API User checkbox within the User Details modal. At that point, you’ll see some of the required information change from a traditional lender user. In the User ID, enter blendapiuser or another name that makes sense to you. In the API Client ID field, enter the client ID that the Blend point of contact provided. Match the First Name, Last Name, and Email fields to the image below. Blend recommends creating a separate persona for this user. See below for more information on that. Save the user.
image-20200427-185650.png

 

Step 5: Please send your Blend Account Manager an email letting them know you successfully completed Steps 1-4 in order to ensure the new integration is enabled.

 

Persona for the Blend API User

As a best practice, Blend very strongly recommends giving the API user the Super Admin persona. This ensures there are no permission roadblocks during implementation and allows for uninterrupted integration cohesion with product development. Credentials for this user are encrypted and cannot be accessed by almost anyone.

If you still have objections to giving the API user the Super Admin persona after discussing with your Blend client-facing teams, you can create a new persona for this API user called “Blend API User.” By creating a separate persona for the API user, you limit the risk of conflicting and changing permissions with other users. Blend recommends adding the following permissions to the Blend API User persona.

Pipeline

Pipeline Tasks

image-20200610-223129.png

Pipeline Tasks cont’d

image-20200610-223203.png

Loan

Other

image-20200610-225158.png

Other cont’d

image-20200610-223349.png

 

Itemization Fee Management – all items checked 

Forms/Tools

Input Forms – all items checked

Tools – all items checked

image-20200610-223622.png

eFolder

General

image-20200610-223924.png

General cont’d

image-20200610-224016.png

General cont’d

 

image-20200610-224109.png

General cont’d

image-20200610-224201.png

General cont’d

image-20200610-224234.png

Unprotected Documents – all items checked

Unassigned Files (File Manager)

image-20200610-224234.png

Unassigned Files (File Manager) cont’d

image-20200610-224725.png

Unassigned Files (File Manager) cont’d

image-20200610-224807.png

Unassigned Files (File Manager) cont’d

image-20200610-224841.png

Protected Documents – all items checked

Conditions – all items checked

Trades/Contacts/Dashboard/Reports

image-20200610-225604.png

Trades – no items checked

Dashboard – no items checked

Contacts – all items checked

Reports – no items checked

Settings

image-20200610-225801.png

Company Settings – no items checked

Personal Settings – no items checked

Other – no items checked

External Settings

image-20200610-225948.png

External Settings – no items checked

Consumer Connect and LO Connect – no items checked

Related articles

Comments

0 comments

Article is closed for comments.