These questionnaires gather the business, technical, and access information the Cloud Maven implementation team needs before configuring Document Insights in your Salesforce environment. Completing them accurately before kickoff reduces delays, testing issues, and rework.
How to complete these forms
-
Everyone completes the Common Prerequisites form (below).
-
Then complete the one add-on that matches your integration:
|
If you're processing… |
Complete this add-on |
|---|---|
|
Bank statements, credit card statements, identity or income documents |
Financial & Identity Documents (MoneyThumb / Ocrolus) |
|
Custom or business-specific forms |
Custom Forms (Lazarus / Google Gemini) |
Processing both document categories? Complete both add-ons in addition to the common form.
Intended audience: Salesforce administrators, business & operations teams, implementation teams, IT & technical stakeholders, project managers, and compliance & security teams.
Common Prerequisites
Complete this form regardless of which integration you're onboarding.
1. Onboarding & Contacts
|
Question |
Response |
|---|---|
|
Primary implementation contact (name, email, role) |
|
|
Expected go-live date |
|
|
Target environment for initial setup |
|
2. Source Object Details
|
Question |
Response |
|---|---|
|
Which primary Salesforce object will the Document Insights component be launched from? |
|
|
Do you need multiple source objects? If yes, list all. |
|
|
Which apps need the Document Insights component or Related List list visible? Example: "Service Console." |
|
|
Which page layouts or Lightning Pages should include the Document Insights component or related list? This component selects or uploads documents and initiates data extraction. Example: "Case Detail page," "Service Console." |
|
|
Which users should have access to this component? |
|
3. Automation Preferences
|
Question |
Response |
|---|---|
|
Should OCR be triggered automatically when documents are uploaded? If yes, specify the automation criteria (field value, status change, record type) |
|
4. Permissions & Access
|
Question |
Response |
|---|---|
|
Which internal users or roles should have access to Document Insights? |
|
Add-on: Financial & Identity Documents (MoneyThumb / Ocrolus)
Complete this in addition to the Common Prerequisites form if you're processing bank statements, credit card statements, or identity/income documents.
1. Provider Selection
|
Question |
Response |
|---|---|
|
Which OCR provider are you onboarding? |
|
2. Document Types
|
Question |
Response |
|---|---|
|
Which document types will you process? |
|
3. Provider Account
|
Question |
Response |
|---|---|
|
Do you have an existing MoneyThumb or Ocrolus account, or do you require a new account to be provisioned? |
|
|
If you have an existing account, who owns and manages the provider credentials on your side? |
|
Add-on: Custom Forms (Lazarus / Google Gemini)
Complete this in addition to the Common Prerequisites form if you're processing custom or business-specific forms.
1. Extraction Approach
|
Question |
Response |
|---|---|
|
Which feature will you use? |
|
2. Sample Documents
|
Question |
Response |
|---|---|
|
Can you provide representative sample forms for each document type? |
|
3. Data Field Mapping
Provide the data fields to extract from each custom form. Every field name must be unique.
|
Field name |
Description |
Maps to Salesforce field |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
4. Extraction & Validation
|
Question |
Response |
|---|---|
|
For Gemini: any specific extraction instructions or prompt requirements? |
|
|
Any validation rules for extracted fields (formats, required fields)? |
|
Thank you for completing this questionnaire. Please return it to your Cloud Maven implementation contact — we'll follow up to confirm details and schedule your kickoff call.