# Writing Consented Data

Understand how, after consent is given, new credentials or data can be provided to a user or recorded about them by authorized parties (like contract owners or automated systems). This covers the rules and methods for data delivery based on established consent.

## The `send` Method with Contract Integration (Recommended)

The simplest way to write credentials while respecting consent flows is using the `send` method with a `contractUri`. This method automatically routes through consent terms when the recipient has consented.

```typescript
const result = await learnCard.invoke.send({
    type: 'boost',
    recipient: 'recipient-profile-id',
    templateUri: 'urn:lc:boost:abc123',
    contractUri: 'urn:lc:contract:xyz789', // Optional: routes via consent if applicable
});
```

When you provide a `contractUri`:

1. **Automatic routing**: If the recipient has consented to the contract, the credential routes through the consent flow
2. **Boost-contract relationship**: When creating a new boost on-the-fly, a `RELATED_TO` relationship is established between the boost and the contract
3. **Permission verification**: The system verifies you have permission to write in the credential's category

{% hint style="success" %}
**Fallback behavior**: If the recipient hasn't consented to the contract, the credential is still sent normally—the contract integration is additive, not blocking.
{% endhint %}

For more details on the `send` method, see the [Send Credentials How-To Guide](/how-to-guides/send-credentials.md).

***

## Writing Credentials to Contracts (Direct) <a href="#writing-credentials-to-contracts" id="writing-credentials-to-contracts"></a>

For more granular control, contract owners can write credentials directly to profiles that have consented using:

* `writeCredentialToContract`: Direct credential writing
* `writeCredentialToContractViaSigningAuthority`: Using a signing authority

```mermaid
sequenceDiagram
    participant Owner as Contract Owner
    participant API as LearnCloud Network API
    participant Consenter as Contract Consenter

    alt Direct credential writing
        Owner->>API: writeCredentialToContract
        Note right of Owner: Includes did, contractUri, boostUri, credential
    else Via signing authority
        Owner->>API: writeCredentialToContractViaSigningAuthority
        Note right of Owner: Includes did, contractUri, boostUri, signingAuthority
    end

    API->>API: Verify consent
    API->>API: Verify boost permissions
    API->>API: Verify category permissions

    opt Via signing authority
        API->>API: Issue credential using signing authority
    end

    API->>API: Send boost with credential
    API->>API: Record write transaction
    API-->>Owner: Return credential URI
```

The system verifies:

1. The recipient has consented to the contract
2. The contract owner has permission to issue the boost
3. The contract terms allow writing in the boost's category

## Credential Syncing <a href="#credential-syncing" id="credential-syncing"></a>

Consented users can sync their existing credentials to a contract using `syncCredentialsToContract`.

```mermaid
sequenceDiagram
    participant Consenter as Contract Consenter
    participant API as LearnCloud Network API
    participant Owner as Contract Owner

    Consenter->>API: syncCredentialsToContract
    Note right of Consenter: Includes termsUri and credentials by category

    API->>API: Verify terms ownership
    API->>API: Update terms with synced credentials
    API->>API: Create sync transaction
    API->>Owner: Notify of synced credentials
    API-->>Consenter: Return success
```

Credential syncing allows:

1. Sharing existing credentials with contract owners
2. Organizing credentials by categories defined in the contract
3. Controlling exactly which credentials are shared

The sync process:

1. Verify the terms exist and belong to the requesting user
2. Ensure terms are still live (not withdrawn or expired)
3. Update the terms by adding the synced credentials to the shared arrays
4. Create a 'sync' transaction with the categorized credentials
5. Notify the contract owner


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.learncard.com/core-concepts/consent-and-permissions/writing-consented-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.