E-Bonding Runbook uses so-called Enablers to communicate with Partner systems. A detailed description is given in the E-Bonding Runbook Concept Guide.
This chapter lists administration recommendations for partners.

Partner ARSAdapter

It's recommended to create a new BAO Remedy Actor Adapter per new Partner. The adapter name can be configured per Partner Configuration in E-Bonding Runbook.
Advantage: This procedure allows the isolation of partner communications. Furthermore, different privileges can be configured per Partner.

Partner ARSAdapter User

It's recommended to use a dedicated Remedy user per Partner ARSAdapter. This user can be configured in E-Bonding Runbook as a so-called "Interface User" (Platform Configuration).
Advantage: Modifications in ITSM can clearly be identified per user.

Partner BAO Role & User

The communication between E-Bonding Runbook Core and E-Bonding Runbook Partner outbound enabler is established via a ORCA Webservices self-call. For the connections a BAO user and an appropriate BAO role is necessary. It's recommended to create for each partner system an own role and user. The role should only have execution permissions on the partner outbound enabler module.