> ## Documentation Index
> Fetch the complete documentation index at: https://help.palletlog.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Invite a partner

> Send an invitation so a partner organization can connect to your Palletlog network.

Invite a **Partner** when you want another organization to join your **Network** and collaborate on movements, confirmations, or shared balances.

<Note>
  Interface labels, screenshots, and step-by-step UI guidance in this article are pending verification against the live Palletlog application. Conceptual guidance below uses approved Palletlog terminology. Detailed UI steps will be added when product sources are confirmed.
</Note>

## Outcome

Your partner receives an invitation and can accept access appropriate to your sharing rules.

## Prerequisites

* Access to the [Palletlog dashboard](https://dashboard.palletlog.com)
* Partner organization name and a contact who can accept the invite
* Asset types you expect to exchange aligned with the partner

<Note>
  If you do not have permission to complete an action in Palletlog, ask a workspace administrator to adjust your role or complete the task for you.
</Note>

## Steps

<Steps>
  <Step title="Add or select the partner">
    Create a partner record if one does not exist, or open the existing partner. See [Add a partner](/partners/add-partner).
  </Step>

  <Step title="Send the invitation">
    Start the invitation flow and enter the contact who should accept on behalf of the partner organization.
  </Step>

  <Step title="Confirm delivery">
    Ask the contact to check email, including spam or quarantine folders. See [Invitation problems](/troubleshooting/invitation-problems) if delivery fails.
  </Step>

  <Step title="Verify network status">
    After acceptance, confirm the partner shows as connected and that shared balance or confirmation access matches your intent.
  </Step>
</Steps>

## Expected result

The partner is connected in your network and eligible for movements, confirmations, and shared visibility according to your configuration.

## Common mistakes

* Inviting a personal email that does not represent the legal entity
* Recording movements before the partner accepts
* Assuming invited partners receive full workspace admin rights — see [Available actions for invited partners](/invited-partners/available-actions)

## Related articles

* [Invite your first partner](/getting-started/invite-first-partner)
* [Accept a partner invitation](/partners/accept-invitation)
* [Shared balances with partners](/partners/shared-balances)
* [Manage partner access](/partners/manage-access)