> For the complete documentation index, see [llms.txt](https://docs.younium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.younium.com/e-signing-integrations/scrive.md).

# Scrive

## Synchronisation scope

| Synchronisation       | Direction        | When it runs                                                |
| --------------------- | ---------------- | ----------------------------------------------------------- |
| Documents for signing | Younium → Scrive | On demand, when a user sends a generated document to Scrive |

Not in scope: signing status, signed documents, cancellation.

***

## Overview

The Scrive integration connects individual Younium users to Scrive, so they can send a generated Younium PDF straight into Scrive to prepare it for signing. Each user connects their own Scrive account rather than the tenant sharing one. Sending a document opens it in Scrive in the browser, where the sender sets up the signing.

## Authentication

Scrive is connected per user rather than per legal entity: each person who sends documents for signing connects their own Scrive account.

You enter your Scrive email address and password once, in Younium. Younium exchanges them with Scrive for a personal access credential and stores that instead — your password is not kept. If Scrive rejects the sign-in, the message it gives is shown and nothing is stored.

Trying to connect when you are already connected is refused rather than replacing the existing connection; disconnect first if you need to connect a different Scrive account.

## Activation (Connect)

Connecting is the activation: a successful sign-in creates your connection and you can send documents for signing straight away.

Because the connection belongs to you, a colleague signing in to Younium does not inherit it — each person connects their own Scrive account before they can send anything.

## Deactivation

Disconnecting removes your Scrive connection from Younium. If you were not connected, Younium tells you so rather than reporting a disconnection that did not happen.

Documents already sent for signing continue in Scrive, and disconnecting does not withdraw or cancel them.

## Print workflow

`Print` accepts entity name, entity ID, file name, and document template ID.

| Younium input                  | Behaviour                                                         |
| ------------------------------ | ----------------------------------------------------------------- |
| `DocumentTemplateId` + entity  | The generated PDF for that entity and template                    |
| The sender's Scrive connection | Identifies who the document is sent as                            |
| Result                         | A link that opens the document in Scrive, ready for signing setup |

## Eligibility

* One Scrive connection per user.
* Print requires prior successful connect and valid template/entity combination.

## Settings

No tenant-level settings entity beyond per-user `ScriveSettings`. `GetSettings` returns the row for the current user or null.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.younium.com/e-signing-integrations/scrive.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
