Define a Named Credential for Peer-to-Peer Scheduling

For effective peer-to-peer review scheduling, create a named credential that makes a REST call to an external system without using a username or password.

Required Editions

Available in: Lightning Experience

Available in: Enterprise and Unlimited Editions with Health Cloud and the Lightning Scheduler Add-On license

User Permissions Needed
To define a named credential Customize Applications

To simplify the setup of authenticated callouts, define a named credential to specify the base URL for the REST callout endpoint and its required authentication parameters in one definition. Salesforce handles all authentication; you can also skip remote site settings for the site defined in the named credential.

By separating the endpoint URL and authentication from the callout definition, named credentials make it easier to maintain callouts. For example, if an endpoint URL changes, you update only the named credential. All callouts that reference the named credential simply continue to work.

Prerequisite: Create an external client app or connected app and an authentication provider.

Important
Important Connected apps creation is restricted as of Spring ‘26. You can continue to use existing connected apps during and after Spring ‘26. However, we recommend using external client apps instead. If you must continue creating connected apps, contact Salesforce Support.

See New connected apps can no longer be created in Spring ‘26 for more details.

  1. From Setup, enter Named Credentials in the Quick Find box, then select Named Credentials.
  2. Click New.
  3. Enter the label and name as UM, and specify the org URL.
    Important
    Important Make sure you use UM as the name, or you can’t schedule peer-to-peer meetings.
  4. Select the following values:
    1. Identity Type: Named Principal
    2. Authentication Protocol: OAuth 2.0
    3. Auth Provider: Use the value of the authentication provider that you set up earlier
    4. Scope: refresh_token full
  5. Select Start Authentication Flow on Save.
  6. Save your changes.