> ## Documentation Index > Fetch the complete documentation index at: https://docs.vestrapay.com/llms.txt > Use this file to discover all available pages before exploring further. # Invite and manage partner users > Use Settings → Partner users in the merchant dashboard to invite a partner, choose what they can see, and change or withdraw their access. This page covers the dashboard side of partners: how to invite one, what each choice means, and how to change or withdraw access. If you have not yet read how partners fit with services and splits, start with [Partners](https://docs.vestrapay.com/partners/overview.md). You manage partners under **Settings → Partner users**. Adding or changing a partner needs full access to **Settings** in your team role, and viewing them needs read access. ## Before you start A partner is tied to the splits of your services, so you need at least one service with split accounts. If you have none, the **Partner users** page tells you to set one up first. See [Splits](https://docs.vestrapay.com/services/splits.md). ## Add a partner user **1. Open Partner users** Go to **Settings → Partner users** and choose **Add partner user**. The **Create a partner user** dialog opens. **2. Enter the partner email** Type the **Partner email**. Use an address that the partner organisation controls. The email identifies the partner across every merchant on Vestrapay, so it cannot already belong to a merchant, team member or Vestrapay staff account. **3. Assign service permissions** Under **Assign service permissions**, choose each service the partner may see, and the splits within it. At least one service, with at least one split, is needed. For each service you also choose the **Base amount display**: | Choice | What the partner sees | | - | - | | Full view | The total the service received, alongside their own share. | | Partial view | Only an amount equal to their own share. | The choice applies to the service as a whole. To give a partner a different view of another service, set it on that service. **4. Create the partner** Choose **Create partner**. The partner appears in your list. ### Choosing splits Choose the splits in a service that the partner is entitled to see. Their share is the sum of the splits you grant. Because access follows the split, you can grant a partner the licence-fee split on an account without granting the levy split on the same account. ### What happens next If the email is new to Vestrapay, the partner receives an invitation to create a password. It is valid for 48 hours, and the partner is shown as invited until they accept. If the email already belongs to a partner of another merchant, the partner is active straight away and receives an email with a link to the partner sign-in page. ## Change permissions To change what a partner can see, open **Settings → Partner users** and choose **Edit permissions** for that partner. The same service and split choices are shown, with the current ones selected. * Add or remove services, splits, or change the Full view or Partial view choice. * Save the changes. The new set replaces the old one for your account, so check that every service the partner should keep is still selected. * At least one service must remain. To withdraw access altogether, suspend the partner. If you restructure splits on a service, come back and review the partners attached to it, so that they still see what you intend. ## Resend an invitation If the partner has not accepted and the link has lapsed or was lost, choose **Resend invite** for that partner. The earlier link stops working, and the new link is valid for 48 hours. Resending is only possible while the partner is still invited. If they have already accepted, there is nothing to resend. ## Suspend and activate * Choose **Suspend** to stop a partner's access to your settlement data at once. Their access to other merchants is not affected. Suspending a partner who is already suspended changes nothing. * Choose **Activate** to restore it. The partner returns to active, or to invited if they never accepted their invitation. ## When something goes wrong The dashboard shows a message when an action cannot be completed. The common causes are below. The error codes are shown for when you contact support. | Situation | What to do | | - | - | | The email already belongs to a merchant, team or Vestrapay staff account (`email_already_registered`) | Use a different address for the partner. | | The partner is already on your account (`partner_already_exists`) | Edit their permissions instead of adding them again. | | The email belongs to a deactivated user (`partner_user_deactivated`) | Use a different address, or contact support. | | A service has no split accounts (`partner_service_has_no_splits`) | Add splits to the service first. See [Splits](https://docs.vestrapay.com/services/splits.md). | | A split is no longer on the service you chose (`partner_split_not_in_service`) | Reopen the dialog, which lists the current splits, and choose again. | | Your merchant account is suspended or rejected (`partners_not_available`) | You cannot add partners or change what they see. Contact support. | | The invitation fails with `partner_access_not_enabled` | Contact [tech@vestrapay.com](mailto:tech@vestrapay.com). | | An action is unavailable to you (`insufficient_module_permission`) | Ask an owner to give your role the required **Settings** access. | See [Errors](https://docs.vestrapay.com/errors.md) for all codes. ## Common patterns **One regulator, two levies on the same account.** Configure two splits on the service, each with its own title and the same account. Grant the partner both splits if they own both, or one if they own only one. They see separate rows by split title inside the settlement, and a single payout to the account. **An auditor across every service.** Add every service with Full view, and every split in each. The auditor sees whole-service totals alongside their own shares. **A parent body with a narrow view.** Use Partial view, so that the partner sees only an amount equal to their own share and never another participant's. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.