The Aline Salesforce managed package puts Aline's contract workflows inside Salesforce. Once it's set up, your sales team can launch Aline templates directly from an Opportunity page, and Salesforce field values — Opportunity, Account, Owner — flow straight into the resulting document. Two people are involved: a Salesforce admin who installs the package, and an Aline admin who connects Salesforce and publishes templates. Setup takes about 15 minutes, and there are no credentials to copy or paste. When your Aline admin connects Salesforce, Aline generates a signing key and writes it into your Salesforce org automatically, and every request the package sends to Aline is signed with that key.
Who Does What
Salesforce admin. Installs the package, assigns the Aline Admin permission set, sets the base URL, manages upgrades.
Aline admin. Connects Salesforce in Aline, then marks which templates appear in the Salesforce launcher.
Sales reps. Launch workflows from an Opportunity. No setup on their side.
Step 1: Install the Managed Package
Log in to the Salesforce org where you want the package (production or sandbox)
Open the stable install link: docs.appnigma.ai/m/aline-sapphire/salesforce-managed-package
Pick an install scope: Install for Admins Only for an initial rollout, Install for All Users once you're ready to open it up, or Install for Specific Profiles for a phased rollout
Approve any third-party access prompts
Wait for Salesforce to confirm the install finished
📌 Coming soon: Aline is going through Salesforce AppExchange security review. Once approved, upgrades will happen automatically. Until then, upgrades ship as new install links.
Step 2: Assign the Aline Admin Permission Set
The package includes an Aline Admin permission set. It does two jobs: it lets a user open the Aline Configuration and Aline Error Logs tabs, and it lets Aline write the signing key into your org. Skip it and the key delivery in Step 4 fails.
Go to Setup → Users → Permission Sets
Open Aline Admin
Click Manage Assignments → Add Assignment
Add yourself and anyone else who should manage Aline config
Sales reps don't need this permission set. They only need access to launch workflows from Opportunities.
Step 3: Set the Aline Base URL in Salesforce
Open the App Launcher and search for Aline Configuration
Enter the Aline Base URL: app.aline.co
Click Save Configuration
If the Base URL Field Is Read-Only
The field is gated behind a custom metadata feature flag. To unlock it:
Open Setup and search Custom Metadata Types
Next to Aline Feature Flag, click Manage Records
Open the record whose Feature Name is Allow_Base_URL_Edit, or create it:
Label: Allow Base URL Edit
Developer Name: Allow_Base_URL_Edit
Feature Name: must be exactly Allow_Base_URL_Edit
Is Enabled: checked
Save, then reopen Aline Configuration
If Callouts Fail With "Unauthorized Endpoint"
Add the Aline host to Remote Site Settings under Setup → Security → Remote Site Settings, using the same host as your base URL.
Step 4: Connect Salesforce in Aline
This is the step that authorizes the integration.
In Aline, open Settings → Integrations
Connect Salesforce and complete the OAuth prompt
Aline pairs with your Salesforce org and writes the signing key into it
Disconnecting Salesforce in Aline revokes the key immediately and the package stops being able to reach Aline. Reconnecting issues a fresh key.
Step 5: Publish Templates to Salesforce
Only templates you explicitly mark show up in the Salesforce launcher, so internal docs stay out of it.
In Aline, open Templates
Turn on Publish to Salesforce for each template you want reps to launch
Dragging a Salesforce field into a template flags it as Salesforce-connected automatically. Templates with no Salesforce fields can still be published, which is handy for NDAs and order forms.
Every published template is visible to every Salesforce user who can launch workflows, so publish deliberately.
Step 6: Launch a Workflow From an Opportunity
Time to smoke-test it.
Open any Opportunity
Find the Aline section and click Launch Workflow
Pick a published template
Check the Review Fields form:
Editable Salesforce fields can be overridden inline before launch
Read-only fields (Created By, Expected Revenue, Owner name) show their current value
Lookup fields show the relationship name, like the Account name, not the record ID
Fill in any Aline-only template fields
Assign an email to every signer role. The workflow can't go to signature until all roles have one.
Click Launch
From the success screen you can Open in Aline or Download the latest synced version. If nothing has synced yet, the Download button is hidden.
One document or workflow can link to several Opportunities, which is useful for a master agreement covering more than one deal.
Upgrading the Package
Until Aline is on the AppExchange, upgrades ship as new install links:
Your account team shares a new install link
Open it while logged into the Salesforce org. Salesforce detects the upgrade and walks you through it
Your base URL, Salesforce connection, and Aline records all survive the upgrade
Troubleshooting
Start with the Aline Error Logs tab, visible to anyone with the Aline Admin permission set. It records HTTP failures like timeouts and unauthorized endpoints, along with business errors Aline returned.
Launch fails with an authorization error. The signing key never reached Salesforce, or it was revoked. Confirm Salesforce is still connected in Aline under Settings → Integrations, that the package is on 0.6.0-6 or later, and that the connected user has the Aline Admin permission set. Reconnect to reissue the key.
Template doesn't appear in the launcher. It isn't marked Publish to Salesforce (Step 5).
Launch button is blocked. A signer role has no email assigned.
Salesforce fields aren't populating. Check that the field API names in the template match the object's real API names in Object Manager. Fields on unrelated objects like Lead won't populate from an Opportunity, because there's no direct relationship.
Download button is greyed out. No document version has synced yet. Launch the workflow and let it sync, or refresh.
"Unauthorized endpoint" on save. Add the base URL host to Remote Site Settings (Step 3).
Best Practices
💡 Install in a sandbox first and test end to end before touching production.
💡 Give the Aline Admin permission set to at least two people so someone can always debug or reconnect.
💡 Publish templates deliberately, since every published template reaches every rep who can launch workflows.
💡 Match Salesforce API field names exactly when building templates.
Next Steps
Publish your first templates to the Salesforce launcher (Step 5)
Review the Aline Error Logs tab so you know where to look if a launch fails
Roll the launcher out to sales reps once your published templates are ready
🎧 Need Help?
Rolling out to a large team, migrating from another CLM, or hitting an error that isn't here? Click Support in Aline or reach out in your shared Slack channel. We can walk your Salesforce admin through the install on a screen share.