> For the complete documentation index, see [llms.txt](https://guide.signspace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.signspace.com/en/managing-signing-requests/protecting-contract-content-with-strong-authentication.md).

# Protecting contract content with strong authentication

When you protect the content of a signature request with strong authentication, you can ensure that only the people added to the signature request can access and view its content.

#### Enabling content protection

You can enable this setting when creating a signature request. In the **Protection** section on the right-hand side of the signature request form, set **Strong authentication required** = ON.

When this setting is enabled, access to the signature request requires strong authentication from every signer and user. The method used to verify identity depends on whether the recipient is an internal user of the organisation sending the signature request or an external user. Separate protection workflows for internal and external users provide ease of use without compromising the level of security.

{% hint style="info" %}
The setting can also be enabled for signature requests created via the API. For external signers, the signer's personal identity code and name must then be provided. This information does not need to be provided for internal signers.
{% endhint %}

#### Verifying the identity of external signers

When contract content is protected with strong authentication, external signers are required to authenticate strongly before they can access the signature process.

The name or personal identity code entered for the external signer in the signature request is compared with the information returned during authentication.

A session protected with strong authentication remains active for 30 minutes. During this time, the signer can sign without having to authenticate again.

If an external signer has a SignSpace account and signs through the application, the identity information previously stored during strong authentication is compared with the name and personal identity code provided in the signature request. The information must match before the signer can be granted access to the signature request content.

When content protection is enabled, the creator of the signature request must enter either the name or personal identity code of each external signer before sending the signature request.

#### Verifying the identity of internal users

User accounts belonging to your own organisation, referred to as internal users, are managed by the organisation's administrators. This enables flexible but controlled access to contract content for users belonging to your organisation.

Internal users who sign or process contracts through the user interface are required to complete strong authentication once in the application. The verified identity is linked to the user's name displayed in the application, ensuring that strongly authenticated users are always shown using their verified official name.

Once an internal user has completed strong authentication, the user can access protected content without having to repeat strong authentication each time they sign in.

If an internal user opens a signature invitation directly from a link in an email and the document requires strong authentication, the user is asked to authenticate before accessing the signature process. The personal identity code stored in the user's account is then compared with the information received during authentication. If the information does not match, or if the user has not yet completed strong authentication in the application, access to the signature process is denied and the user is directed to sign in to SignSpace and complete strong authentication there.

#### Adding users

Only owners, reviewers, additional recipients and groups from your own organisation can be added to protected signature requests.

{% hint style="warning" %}
**Note:** External users who have been added to an internal group will gain access to the signature request through the group. Please take this into account from an information security perspective.
{% endhint %}

Each internal user must verify the user's identity using strong authentication while signed in to the SignSpace account before access can be granted.

Signed-in users are always required to complete strong authentication during the signing process if the signature itself requires strong authentication.

#### Charges for content protection

Strong authentication performed during signing to access protected content is free of charge. If a signer requires additional authentication attempts to access the protected content or complete the signing process, the organisation that sent the signature request will be charged according to the [price list](https://signspace.vastuugroup.fi/hinnasto).
