> 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/sharing-a-signature-request.md).

# Sharing a signature request

You can share a signature process with users in your organisation as well as with external recipients.

Sharing is useful, for example, when other representatives of the contracting party, in addition to the signer, need to access the documents or participate in conversations.

If the recipient does not have a SignSpace account, they can access the shared content directly through a secure link sent by email. No SignSpace account is required.

#### Sharing a signature process with an external recipient

When you share a signature process with an external recipient, they receive an email notification about the content shared with them.

Through the link in the email, the recipient can:

* open the signature process shared with them
* review the shared documents and information
* participate in the conversation, if conversations are enabled.

#### Accessing shared content without a SignSpace account

If the recipient does not have a SignSpace account:

1. The recipient opens the link received by email.
2. SignSpace sends a verification code to the email address with which the content was shared.
3. The recipient enters the verification code.
4. After verification, the shared content opens.

<div align="left"><figure><img src="https://1628421867-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJb1iIhXKdH5Zdj1H5Ksy%2Fuploads%2FopTCdx3f535Ekohu5BFa%2Fimage.png?alt=media&amp;token=d1acf207-20ac-49b9-aab7-d9b168191cfc" alt="" width="563"><figcaption></figcaption></figure></div>

#### Participating in a conversation

If conversations are enabled, an external recipient can participate in the conversation related to the signature process through the shared view.

If conversations are not enabled, the recipient can view the shared content but cannot participate in the conversation.

#### Security of shared content

Access to shared content is protected. If the recipient does not have a SignSpace account, their access is verified using a verification code sent by email.

The email states how long the link to the shared content remains valid.

The user session remains valid for 30 minutes. After the session expires, the recipient must verify their access again.

{% hint style="info" %}
If the signature request is separately protected with strong authentication, it cannot be shared with external users.
{% endhint %}