Contract room settings control how documents are signed, verified, tracked, and managed across your entity. As an administrator, you configure default behaviors that apply to all contracts sent by your team , though individual settings can be adjusted per document during the sending process.

Important: Contract room settings differ from Deal Room settings. This article covers Contracts only. Deal Rooms have their own feature and functionality controls.

Navigate to your settings via the profile icon in the top-right corner:

From Document Settings, you can configure all contract defaults. Changes apply to all new

documents; existing sent documents retain their original settings.

Control how recipients sign your contracts and what verification methods are required.

Toggle Sign with electronic identification to make eID available as a signing method across all documents by default. eID provides Advanced Electronic Signature (AdES) level verification, offering higher identity assurance than basic click-to-sign.

When enabled, recipients see eID options matched to their country (BankID in Sweden, BankID NO in Norway, MitID in Denmark, FTN in Finland, and others). eID can be deactivated on individual documents if needed.

For detailed country support and setup, see Supported eID by country and How to activate Electronic Identification (eID) signing for a document.

Toggle Enable QES signing to offer Qualified Electronic Signature, the highest eIDAS signature level. QES is legally equivalent to a handwritten signature across all EU Member States and is visible in Adobe Acrobat document properties without requiring a separate certificate.

QES is available on Professional and Enterprise Plus plans. When enabled, senders can toggle "Sign with QES" before sending , but if selected, all recipients must use QES (mixing methods is not allowed).

Learn more in Qualified Electronic Signature.

Configure which signing methods recipients can use:

These settings control what appears in the signing flow. At least one method must be enabled.

Configure how senders (document creators) interact with the signing process:

Note: If you enable QES, the sender must add themselves as a recipient and cannot use the "Sign on send" option.

Control how recipients interact with documents and what visibility you have into forwarding behavior.

When enabled, GetAccept tracks if a recipient forwards the document to someone new. You'll see the new recipient appear in the document's recipient list with "Forwarded by [original recipient]" noted. This helps you understand if deals are expanding to new stakeholders.

Toggle to allow live chat communication between senders and recipients directly within the document. When enabled, recipients can initiate conversations, and senders receive notifications. Chat is available on both signable and non-signable documents.

When enabled, recipients can forward the signing responsibility to another person without losing the document trail. The new signer completes the signature, and you see both the original recipient and the actual signer in the audit log.

By default, recipients can only download the document after signing (as a signed PDF). Enable this setting to let recipients download before signing , useful for recipients who want to review offline or share internally before committing.

When enabled, recipients must explicitly agree to electronic signature terms before signing. This adds a legal consent step to the signing flow, recommended for contracts with strict compliance requirements.

Manage how long documents remain accessible and what happens after they expire.

Set the default number of days before a sent document expires (default: 14 days). After expiration, recipients cannot open, sign, or interact with the document. You can extend an expired document's deadline after it expires without recreating it , no need to resend.

Configure automated reminders for contract renewals stored in AI Contract Management. Set reminder timing for upcoming renewal dates and renewal notice requirements.

GetAccept sends three automated reminders during the signing lifecycle. Configure timing for each:

Adjust timings based on your typical deal cycle. Shorter cycles warrant faster reminders; longer deals benefit from more generous windows.

Control what happens after all recipients sign.

Optionally set a custom URL where signers land after completing their signature. Leave blank to keep recipients on the GetAccept page. Common uses: thank-you pages, next-step instructions, or external payment processors.

Specify email addresses that should receive the signed PDF and signing certificate automatically. For example, add finance@company.com to archive contracts without making them GetAccept users. Multiple emails can be added, separated by semicolons.

The signing certificate (audit log of all signing activity) is generated automatically after all parties sign. Configure the language the certificate appears in and whether additional details are included.

Set default communication templates for various document events. Templates control the email subject, body, and optional SMS messaging when documents are sent, reminded, or signed.

Four message categories are available:

Each template can be customized with merge tags (e.g., `########{{recipient.first_name}}`, `########{{document.name}}`). You select which template is used during the sending process, so you can maintain different templates for different deal types.

For guidance on creating and editing templates, see How to create and use communication templates.

Create and manage tags to categorize and filter contracts. Tags help you organize documents by deal type, segment, geography, or any custom classification.

Tags are created at the entity level in Entity Settings → Content Tags. Once created, they appear in Document Settings and can be applied to individual documents. Filter by tags in the Documents tab to quickly find related contracts.

For setup details, see How to set up and manage document tags.

Control document visibility and whether recipients can share the document link with others.

When enabled, the document is accessible only to invited recipients. Anyone who receives the link cannot open it , forwarded links do not work. This ensures strict access control for sensitive agreements.

When private mode is off, recipients can forward the document link to others. GetAccept tracks new viewers (if "Identify new recipients" is enabled) but the document remains accessible to anyone with the link.

Understand how settings apply to different document types:

Document type is selected when creating a new document and determines which settings are relevant in the sending flow.

For high-risk or regulated contracts: Enable eID or QES signing, e-sign consent, and consider shorter expiration periods (7-10 days) to ensure timely execution.

For standard B2B agreements: Use click-to-sign (basic electronic signature) with a 14-day default expiration. Enable chat for buyer collaboration. Identify new recipients to track stakeholder expansion.

For simple quotes or proposals: Non-signable documents with longer expiration (30 days). Chat optional. No special verification needed.

For multi-party agreements: Set explicit signing order, enable signature transfer if flexibility is needed, and use communication templates that remind all parties of their step in the process.

For renewal tracking: Use AI Contract Management with renewal reminders configured. Tag contracts by renewal type so you can filter and report on upcoming renewals.