Skip to content

Settings

These settings are on the E-signature tab of the Sliick Docs Settings page. All of them have sensible defaults, so you can send your first document without changing any. The ones on this page are worth a decision before you go live. The two settings you must fill in before anything can be sent are covered in One-time org setup.

The tab lists its sections down the left-hand side. Click one to jump to it. Every section is still on the page if you prefer to scroll.

Every signing link expires. Set the default in Default signing window (days), from 1 to 365 days. If you leave it alone, links last 2 days. A sender can choose a different window for a single request when they send it.

Once a link expires, it no longer opens, reminders stop, and the request moves to Expired overnight.

The Signing rules settings, with a reminder schedule of 3, 7 and 14 days and the confirmation to start automatic reminders

Reminders are sent by hand until you turn this on. In Automatic reminder schedule (days), enter up to six whole numbers in increasing order, separated by commas, for example 3,7,14. Every signer who has not signed or declined is reminded that many days after they were invited. Before it starts, you are asked to confirm, and told how many requests are currently waiting on a signer.

  • Blank means off. An upgrade never turns it on for you.
  • Days count from each signer’s own invitation. In a request signed in order, later signers get their own schedule rather than a pile of overdue reminders.
  • If several reminder days were missed, the signer gets one catch-up reminder, not several.
  • Reminders stop when the request expires. They skip anyone who has signed or declined, and they never land on top of a reminder you sent by hand.
  • A signer who is part-way through signing is skipped, and reminded once they have stopped.

Who can turn it on. Turning reminders on, or sending more of them, needs the Sliick Docs Admin permission set. The System Administrator profile on its own is not enough. Turning reminders off, or sending fewer, does not need it, so an admin can always switch them off.

Save it as a service account. In Salesforce, a scheduled job belongs to the person who scheduled it. If that person is later deactivated, reminders stop, even though the setting still shows them as on.

  • Where you can, save the schedule while logged in as a service or operations account (using Log in as). Service accounts are not deactivated when someone leaves.
  • If the owner is deactivated anyway, any admin can fix it by saving the reminder schedule again. Sliick Docs then runs reminders as that admin. Saving other settings never disturbs a working schedule.

The Settings page shows which user reminders run as, and warns you if that user is inactive.

The Signing emails settings: Email branding with the brand name, accent colour, logo and a header preview, and below it the Invitation email subject and message

You can edit four emails: invite, reminder, cancellation and completion. For each, set a subject and body. Merge tags let you include the document name, the sender’s name, the recipient’s name, the expiry, the sender’s personal message, and the request’s short reference code.

The built-in emails lead with the document name and the sender’s name. That is deliberate: someone deciding whether an unexpected email is genuine needs a name they recognise, and an internal reference number looks like phishing. Write your own wording the same way.

Always added, whatever you write: the signing link, the expiry line and a short anti-phishing footer are added after your text, so they cannot be removed or changed. The verification-code email is fixed and kept short.

Branding. Add your organisation’s name, an accent colour and a logo. The brand-name box shows the name that will be used if you leave it alone. Upload a logo, or paste the address of an image you already host. Logos you upload are kept, so you can switch back to an earlier one without uploading it again. Emails already sent keep the logo they were sent with. Use the preview and the test-email button before you go live.

The same accent colour and logo appear on the signing page and the public verification page. A Brand mark setting on each page decides whether it shows nothing, your logo, or your name in words. See One-time org setup.

There are two separate retention settings. Which one applies to a request is fixed when it is sent, so deleting a template later does not change requests already sent from it.

  • Requests sent from a template follow that template’s own signature retention setting. The default is to keep files forever.
  • Requests sent without a template (any picked or uploaded PDF) follow Delete signed files for envelopes sent without a template (days) on this tab. Enter 0 to keep files forever, which is the default. This setting never affects requests sent from a template.

When the time is up, the nightly sweep permanently deletes the Certificate of Completion and the signed PDFs. The request itself is kept as the signing record, including its participants, the values they entered, and its full history.

Deletion cannot be undone. So when you turn retention on or shorten it, you are asked to confirm and told how many requests will be affected straight away. Time is counted from the completion date, so turning it on in an org with older completed requests deletes those files on the first night, not gradually. Lengthening the time, or going back to keep forever, needs no confirmation.

Legal hold is a tick box on an individual request. While it is ticked, the sweep leaves that request alone.

Note: these settings are separate from the retention for generated documents. See Compliance.

By default, a completed document carries a visible signature stamp and comes with a Certificate of Completion, the evidence record kept in your org. This runs natively in Salesforce, needs no set-up beyond this guide, and is the right choice for most documents.

Some organisations need the signed PDF itself to carry a digital seal, so it opens as certified in a standard PDF reader such as Adobe Acrobat. For that, choose a different Signature mode on this tab.

Signature modeWhat a completed document carries
Tier 0 - Audit trail + Certificate of Completion (default)The visible stamp and the certificate. No digital seal on the PDF. Native, with no outside connection.
Tier 1 - Self-signed (test-drive of the certified seal)A working seal that is for testing only. It behaves like the certified tiers, so you can try the whole process, but PDF readers show the signature’s validity as unknown because the seal is not from a trusted source.
Tier 2 - Bring your own certificateA seal made with your organisation’s own trusted certificate. Once linked, this section shows the certificate’s name, who issued it, and when it expires.
Tier 3 - Certified seal (AdES), sealed in your organization’s nameA seal from a trusted certificate authority, in your organisation’s verified name. Documents open as certified and unaltered in standard PDF readers.
Tier 4 - Qualified seal (QES, EU)A qualified electronic seal for EU-regulated work (eIDAS QES), issued by an accredited provider after your organisation’s identity is verified.

Tiers 1 to 4 must be set up for your org first. Picking one is not enough: until your org is set up for it, saving is refused with a message naming the mode. This means a seal mode is never switched on before it can actually work. These tiers use a Sliick service to apply the seal. Talk to the team if a sealed tier is relevant to you.

If the seal is delayed, the signed copy waits for it. On a sealed tier, recipients receive the sealed PDF. If sealing does not work first time, delivery is held and retried automatically for about an hour, and the request shows Sealing - delivery pending on the Sliick Signatures card. The copy goes out by itself once sealing works. If it still has not worked after that, the request shows Sealing failed - retry, the sender is emailed, and the Retry sealing action starts again.

The tier a request is sent under is fixed when it is sent. Changing the Signature mode later does not change requests already sent.