Install and connect Salesforce

Check these first.

Revenue Cloud, Quotes and Orders aren't required: the package installs in any supported org, and you can send from opportunities, contracts, accounts, cases, custom objects or any other object. When Quotes or Orders are on, connecting adds what goes with them (see What Tally Sign adds to your org).

Pick the Salesforce user Tally Sign will connect as. Tally Sign works in Salesforce as this user:

• A System Administrator, or a dedicated user with a full Salesforce license and the API Enabled, Customize Application, Modify Metadata, Assign Permission Sets and View Setup and Configuration permissions.
• The user must be able to sign in to Salesforce in a browser. API-only users and the free Salesforce Integration license can't connect.
• Salesforce updates are made as this user, and automation rules fill documents with the fields this user can see.

In Tally Sign, open Settings → Salesforce. Setup starts with one question: which Salesforce records does your team send documents from? Pick every one that applies. Setup then covers only those, and Check Salesforce looks for Tally Sign on each of them.

Anyone can see the answer in Settings → Salesforce; owners and admins can change it any time. Watch how, at the top of the setup card there, opens this walkthrough with your answer already picked.

1. 1In Tally Sign, open Settings → Salesforce.
2. 2Under Where will you send from?, pick every place your team sends from.
3. 3Under Where does your org sign in?, choose Production, Sandbox or Custom domain. For a custom domain, enter your My Domain, for example northbeam.my.salesforce.com. You can also paste any Salesforce address from your browser's address bar; Tally Sign shows the My Domain it will use.
4. 4In step 1, Install Tally Sign in Salesforce, choose Install in Salesforce. It opens your org's install page for Tally Sign App in a new tab.
5. 5Sign in to Salesforce as an admin, choose Install for Admins Only and choose Install. Reps get access later with the Tally Sign User permission set.
6. 6When Salesforce asks you to approve third-party access to https://app.tallysign.com, check Yes, grant access to these third-party web sites and choose Continue. Installing takes about a minute.
7. 7When it says Installation Complete!, choose Done. Tally Sign App is listed in Setup → Installed Packages.

1. 1Back in Tally Sign, in Settings → Salesforce, go to step 2, Connect your org, and choose Connect Salesforce.
2. 2Sign in to Salesforce as the user you picked and choose Allow.
3. 3You're sent back to Tally Sign, which shows Connected.

Connecting links the package to your Tally Sign account and gives the Salesforce user you connected as the Tally Sign Admin permission set. If the user is missing one of the permissions above, Settings → Salesforce says which one and what it stops Tally Sign from doing. Give the user the permission and choose Refresh next to your org, or connect as a different user.

If you picked A custom object, choose it now under Where you send from, the first step of Setup (see Custom objects).

Next, give reps access and put Tally Sign on your record pages: see Add Tally Sign to Salesforce.

After connecting, Settings → Salesforce starts with your org: its name, Production or Sandbox, and Connected (or what's wrong), with the Salesforce user Tally Sign works as and the last sync. Below it, Setup lists what's done and what's left, one step at a time (see Check Salesforce). Your org lists what Tally Sign found: Revenue Cloud, Quotes, Orders, Contracts, Salesforce CPQ, Billing, Multi-currency and the Tally Sign package with its version. What your org doesn't have is listed on one line under Not found, and skipped.

• Connected as shows the Salesforce user Tally Sign works as, and Last sync when Tally Sign last wrote to Salesforce.
• Choose Refresh next to your org after you turn something on in Salesforce, or after installing or updating the package.
• The … menu next to it has Change Salesforce user, Connect another org, Connection details (the org ID, who connected it and when) and Disconnect.
• Anything that needs you shows at the top of the page, with what to do and a button to fix it or check again.

The package itself doesn't use Quotes, Orders, Cases, CPQ or your custom objects, so it installs in any supported org. Connecting (or Refresh) adds what goes with the ones you have and send from:

• Access to the new lookups comes from a permission set Tally Sign creates, Tally Sign Quotes and Orders. Tally Sign assigns it to everyone who has Tally Sign Admin or Tally Sign User each time you connect or choose Refresh. Gave someone access since? Choose Refresh, or assign it yourself.
• Add Send with Tally Sign to the Quote, Order and Case page layouts like on other objects (see Add Tally Sign to Salesforce).
• Turned on Quotes or Orders after connecting? Choose Refresh in Settings → Salesforce.
• Without them, every envelope still records the record it was sent from (Related Record), and Account, Opportunity and Contract lookups fill in as usual.

To send from cases, for example a service report the customer signs after a visit, open Settings → Salesforce and pick Cases under Where will you send from? (once you're connected, it's Where you send from, the first row of Setup). When you connect (or right away, if you're already connected), Tally Sign adds Send with Tally Sign to Case and a Case lookup on Envelopes.

• Put the component and the action on the Case record page like any other object: see Add Tally Sign to Salesforce. To show a case's envelopes, add the Envelopes related list to the Case page layout.
• Link the template to Case in the editor. The case's contact is the customer signer by default (see Who signs).
• Already added your own lookup to Case on Envelopes? Tally Sign uses yours and doesn't add another.

To send from your own object, for example a Service Agreement (Service_Agreement__c):

1. 1In Tally Sign, open Settings → Salesforce. Under Where will you send from?, pick A custom object.
2. 2After connecting, under Where you send from (the first row of Setup), choose the object from Pick a custom object and choose Add. The list shows your org's custom objects.
3. 3Leave Show envelopes in a related list on to add an Envelope lookup to the object. Tally Sign fills it in on every envelope sent from one of its records.

Tally Sign adds Send with Tally Sign to the object right away. Then put the component and the action on its record page like any other object: see Add Tally Sign to Salesforce. To show the record's envelopes, add the Envelopes related list to the object's page layout.

A template for the object is linked to it in the editor: see Salesforce fields in templates.

When a newer version of the package is out, the Setup card in Settings → Salesforce shows Package update available with the version you have and the one available. Choose Update in Salesforce (or Copy link to send it to your Salesforce admin), install the update, then choose Refresh next to your org. The link opens your own org's login (its My Domain, or test.salesforce.com for a sandbox), so a sandbox update can't land in production by mistake. Your envelopes and settings are kept.

To move Tally Sign to another Salesforce user, for example before the admin who connected leaves, open Settings → Salesforce and choose Change Salesforce user in the … menu next to your org. Sign in to Salesforce as the new user and choose Allow. Nothing is disconnected: sending, syncing and automation keep running. Only users from the connected org are accepted.

You can connect your production org and one or more sandboxes at the same time. Each org sends and syncs on its own, and envelopes from a sandbox never show up in production, even when record ids match. Install the package in each org you connect.

1. 1In Settings → Salesforce, open the … menu next to your org and choose Connect another org.
2. 2Choose Sandbox (or Custom domain with the sandbox's My Domain), install Tally Sign in the sandbox with step 1, then choose Connect Salesforce.
3. 3With more than one org connected, Settings → Salesforce lists them under Salesforce orgs. Choose Work in this org next to the org you want to set up. Template fields, automation rules, seats and record search in Tally Sign use that org. Everyone else stays on production until they switch.

• Emails from a sandbox. Sandboxes copied from production have real customer contacts. By default, signing emails for anyone outside your company go to the person sending instead, and the send form says so. To test with real recipients, turn on Email real recipients from this sandbox.
• One production org. Connecting a different production org doesn't replace the one you have. Tally Sign asks first, and Replace production org disconnects the old one.
• Refreshed sandbox. After a sandbox refresh, connect it again. The old copy is disconnected, and its automation rules can be moved to the new copy from Automation.
• One company per org. A Salesforce org can be connected to one Tally Sign company at a time. If it's connected elsewhere, Tally Sign asks before moving it, and the other company's admins are emailed.

When Salesforce refuses the sign-in, Settings → Salesforce says what happened and what to do, and keeps it on the page until you dismiss it. The usual causes:

If Tally Sign can't reach Salesforce later, your org shows Not working with the reason and either Reconnect or Check again, and a banner across the top of Tally Sign says so until it's fixed. Owners and admins also get an email. In Salesforce, reps see a short message asking a Tally Sign admin to reconnect, and admins get a link to these settings. Updates that happen meanwhile (envelope status, write-backs, signed PDFs, orders) are kept and sent as soon as it's fixed. Updates held for more than 30 days wait for you to choose Retry.

If Salesforce refuses an update, for example because of a validation rule, a locked record or a field the connected user can't edit, Tally Sign tries again on its own for about four days. Updates that still fail, or that can't work by trying again, are listed in Settings → Salesforce under Salesforce updates that need attention, with the document and Salesforce's message, and owners and admins get an email. Fix the cause in Salesforce, then choose Retry (or Retry all). Steps that already went through aren't repeated, so no second order, contract or PDF is created. Choose Dismiss if you finished it by hand; its error also leaves the envelope's Last Error.

Disconnect, in the … menu next to your org in Settings → Salesforce, stops sending from that org and syncing back to it. Its automation rules are turned off and their Flows are removed from Salesforce. The rules stay in Automation, where you can delete them or move them to another connected org. Documents already sent can still be signed. Updates wait until you connect the same Salesforce org again (up to 30 days), then catch up. Your templates and settings are kept.