Checklist for new firms using Symphony Messaging embedded in a Partner platform

Certain prerequisites are necessary to be able to access Symphony Messaging embedded in a Partner platform. These depend on whether you are a standard Symphony customer, or you have been granted / intend to get Sponsored Access.

Note: To check whether a Symphony Messaging instance is already set up for your firm, refer to this article.

Prerequisites for standard Symphony customers

  1. Enable third party cookies in the users' browser.
  2. Provision a Symphony Messaging account for the unlicensed users (for more details, see the section Creating end-user accounts in the latest Symphony Messaging Admin Portal Guide).
  3. Enable external communications for users (for more details, see the section Enabling external communications in the latest Symphony Messaging Admin Portal Guide).
  4. Request users to enable Auto-accept connection requests in their Symphony Messaging settings
  5. Enable new room members to view conversation history (for more details, see the section Instance-level entitlements supported by Symphony Messaging in the latest Symphony Messaging Admin Portal Guide)
  6. (Optional) Activate Single Sign-On on the Symphony Messaging tenant.

Note: Only standard Symphony customers can configure SSO. If you have been sponsored via a Partner or via a Sponsored Access request, you will either be using the Partner’s SSO, or need to set up a dedicated password to access Symphony Messaging.

  1. Make counterparty groups discoverable.

Prerequisites for Sponsored Access users

  1. Enable third party cookies in the users' browser
  2. Make counterparty groups discoverable.