• English
  • Customer relations

    A relation connects a managing customer to a participant customer in one shop. Both roles use native PrestaShop customers, and a customer cannot manage themselves.

    Use the global relation page

    Open Customers > Participants Manager. The page lists relations in the employee's permitted shop context.

    To create a relation:

    1. Select the shop when more than one permitted shop is in context.
    2. Use Search for managing customer and Search for participant.
    3. Select two different eligible customers.
    4. Confirm the relation.

    An existing active relation is not duplicated. An inactive relation must be explicitly reactivated.

    Work from a native Customer page

    The Participants Manager card on a Customer page separates:

    • participants managed by the displayed customer;
    • customers managing the displayed customer.

    Use Add participant or Add managing customer to keep the displayed customer fixed in the appropriate role. If no customer matches a valid email address, employees with the required permissions can continue through PrestaShop's native customer-creation form. This workflow is available in a single-shop context and creates the relation after successful customer creation.

    Manage relation permissions and lifecycle

    The action menu can provide:

    • Edit permissions for booking, address editing, and birth-date editing;
    • Deactivate or Reactivate;
    • Permanently delete.

    Deactivation retains the relation and its stored permissions. Reactivation reuses them. Permanent deletion is currently available because the module does not store other data that directly references the relation itself. It cannot be undone, but it does not delete either customer or persisted order participation.

    For a managed participant, active managing customers receive the supported effective capabilities even when stored relation permissions are narrower. For a self-managed participant, stored permissions are effective. A not-initialized historical participant also uses stored permissions until an administrator initializes account management.

    The card and mutations require the corresponding Participants Manager and native Customer read, create, update, or delete permissions. Links to related orders additionally depend on native Order access.