These settings are applied to all invitations sent by any Workspace member, so you can reduce mistakes, improve signer completion rates, and enforce consistent security/compliance behavior—without training every sender.
Settings are available only to Workspace administrators and can be configured in the Administration Portal in the Workspace Settings section.
Settings
Team Space Settings
Directory where to save document copies sent from Team space (become public or stay personal)
It decides where copies go when documents are sent from Team Space—and whether those copies stay visible to the whole team or live only in someone’s personal space. This helps keep important files easy to find, ensures team records stay in one place, and reduces the risk of sharing something more widely than intended.
Recommended use:
Choose Team Space/public when the team needs visibility (shared workflows, coverage, handoffs).
Choose personal when senders need private working copies while still sending from shared assets.
Signing Settings
Choose how signers can open documents when signing via mobile devices
Choose how signers open documents on mobile devices—whether they sign in a mobile browser, the mobile app, or get to choose between the two. This gives you control over the signing experience and lets you match it to how your signers prefer to work on their phones or tablets.
Don't save signer signatures and initials when completing a document
Control whether signer signatures and initials are saved after a document is completed. Turning this off means signatures are used only to finish the document and aren’t stored for future reuse, which can better match stricter privacy or security requirements.
Offer to automatically apply signature and initials to all corresponding empty fields in a document after filling out the first field
After a signer fills in their first signature or initials, the same information is automatically placed into all other matching empty fields. This reduces repetitive work and helps ensure no required signature or initial is missed.
Require Signers to Use Only Hand Drawn Signatures
Limit signing to hand-drawn signatures only, excluding typed or image-based options. This is useful when your policies or local requirements call for a more traditional signing method.
Hide the «Decline to Sign» option from signers
Remove the option for signers to decline directly from the signing flow. This encourages signers to complete the document or follow your preferred process if they have questions or concerns.
Display the electronic signature disclosure consent agreement
Control whether signers inside or outside of your workspace see the electronic signature consent agreement before signing. This lets you align the experience with your legal requirements or internal policies. You will be given an option to display the default SignNow signature disclosure or customize it.
Choose how signers will be guided through document fields
Decide how signers move through required and optional fields so the signing flow matches the complexity of your documents and reduces missed fields.
Send to Sign Settings
Require a custom email subject when sending documents for signing
Requiring a custom email subject when sending documents for signing helps ensure that recipients immediately understand the purpose of the email. This creates a more professional experience, provides clearer context, improves email open rates, and reduces follow-up questions such as “What is this for?” It is especially useful in environments where multiple departments send signing invitations and consistent subject line standards are important.
Force two-factor authentication for document Invites (via a phone call, SMS or password)
Forcing two-factor authentication for document invites adds an extra layer of identity verification before recipients can access signing links. This significantly reduces the risk of unauthorized access and strengthens overall document security, particularly when sharing sensitive information or sending documents to external recipients.
📝 Once the required custom email subject and enforced 2FA are enabled, the Workspace users will see the toolptips indicating that these settings must be configured on the Invite Page.
Qualified Electronic Signature (QES)
Turning on Qualified Electronic Signature (QES) enables signing workflows that meet higher legal and regulatory standards where QES is required. This setting ensures compliance in regions or business processes that mandate the use of qualified electronic signatures.
📝 Qualified Electronic Signature is a corporate-level feature that requires additional payment. Contact our Sales team through the Contact form for further information and pricing.
Actions After Signing
Sign downloaded documents with a digital certificate
Signing downloaded documents with a digital certificate ensures that exported files retain cryptographic proof of integrity even after they leave the platform. This is particularly useful when documents are archived in external systems, shared with third parties, or stored long-term, as the certificate allows recipients and auditors to verify that the file has not been altered since download.
Add a watermark to downloaded documents
Adding a watermark to downloaded documents helps clearly communicate document status (such as “Copy” or “Downloaded Version”) and discourages misuse or unauthorized redistribution. This setting supports internal governance and controlled distribution, especially when documents are shared widely across teams or outside the organization. Leaving the watermark disabled may be appropriate when distributing finalized documents intended for official use or customer delivery.
Redirect Recipients
After completing the document
After declining the document
After saving progress and closing the document
After canceling the invite
Recommended patterns:
Completion: A “Thank you” or confirmation page with clear next steps, such as downloading a copy, making a payment, or returning to an internal portal.
Decline: A support or contact page, or an alternative workflow that allows the recipient to explain why they declined or choose a different option.
Save & close: An instructional or reminder page explaining how to resume signing and what information may be needed next.
Cancel invite: An informational landing page that reduces confusion if a recipient follows an outdated or stale link, and directs them to the appropriate point of contact.
Emails Settings
Document completion email attachments
This setting controls whether completed documents are included as attachments in the document completion email. Including attachments allows recipients to immediately access the finalized files from their inbox, while disabling attachments reduces the risk of unintended forwarding or uncontrolled distribution. Organizations often choose different approaches depending on document sensitivity and internal security policies.
Receive email notifications when signers open documents
Enabling email notifications when signers open documents provides visibility into recipient engagement. This can help teams understand whether an invite has been seen and supports timely, informed follow-ups, particularly in workflows where responsiveness or deal momentum matters.
Attach documents with history to completion emails
Attaching documents with history to completion emails ensures that recipients receive not only the finalized document but also its signing and activity record. This makes completion evidence readily available to stakeholders who may not log into the product, provided this aligns with organizational compliance and record-keeping policies.
Login Settings
Enable/Disable login via social networks
This setting determines whether workspace members can sign in using social network accounts instead of email-and-password authentication. When social login is enabled, members may authenticate through supported social providers, which can simplify access and reduce friction during sign-in. When disabled, all members must use the standard authentication methods defined by the workspace, such as email and password or single sign-on (if configured).
Changing this setting affects the entire workspace. If social login is disabled, members who previously relied on social network sign-in will need to switch to an alternative login method to access their accounts. This may require them to set or reset a password or follow identity verification steps, depending on existing account configuration. Disabling social login is commonly used to standardize access methods and align authentication practices with stricter organizational security policies.
Additional Settings
Export documents with history to cloud storage
This setting controls whether documents, along with their signing history, are automatically exported to a connected cloud storage solution. Enabling this feature ensures that all signed documents are archived with their audit trails, which is useful for compliance, record-keeping, and maintaining an organized digital archive. If this setting is disabled, documents will not be automatically exported to cloud storage, and alternative manual export processes may need to be followed.
Connect your "Drawloop for Salesforce" account
Connecting your "Drawloop for Salesforce" account integrates document generation and automation workflows with your Salesforce processes. This allows you to streamline document creation and management directly within the Salesforce environment. If this connection is not set up, your Salesforce processes will not be linked to Drawloop, potentially requiring manual document handling or alternative automation solutions.
Enable/Disable SignNow AI
Enabling SignNow AI provides access to artificial intelligence-powered features. Disabling AI means these features will be unavailable to workspace members, centralizing control over when AI features are used within the organization. Disabling this setting may be appropriate if you're piloting AI capabilities, restricting its use based on internal policies, or waiting for full organizational readiness.
Enable/Disable payment request setup
This setting governs whether users can set up payment requests within the workspace. Enabling payment request setup allows members to create payment flows as part of document signing processes. Disabling it restricts payment request capabilities, ensuring that only authorized teams or individuals can initiate payment requests, thereby controlling payment-related activities within the organization.
Enable/Disable branding setup
Enabling branding setup allows workspace members to customize the appearance of outbound communications, including email notifications and document templates, ensuring they reflect your organization’s branding. Disabling this setting restricts customization options and prevents accidental changes to the branding, which is typically managed by a central marketing or operations team. This ensures that brand consistency is maintained across all communications.
📝 Some settings—such as cloud storage exports, payment requests, and similar integrations—may be available at both the account level and the workspace level. When a setting exists in both places, the workspace-level configuration takes priority and overrides the account-level setting for all members of that workspace. This allows organizations to apply global defaults at the account level while enforcing more specific rules or exceptions at the workspace level.
You can reset all workspace settings to their default values. When this action is completed, every customized workspace configuration will be reverted to the original default state. This includes security controls, notification preferences, integrations, branding options, and any other workspace-specific settings.
This operation is irreversible. Once the reset is performed, all current settings will be permanently lost and cannot be recovered. Workspace members will immediately be affected by the default configurations, which may change their access, available features, and workflow behavior. Before proceeding, ensure that all stakeholders are aware of the impact and that any required settings are documented so they can be reconfigured if needed.













