> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rings.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Perplexity

> Add Rings as a custom remote connector in Perplexity

<Note>
  Custom connectors require a paid Perplexity plan. On Enterprise, admins must
  first enable **Allow members to add custom connectors** — it is off by
  default.
</Note>

<Steps>
  <Step title="Open connector settings">
    * **For yourself:** **Account settings → Connectors**
    * **For the whole organization (admins):** **Enterprise settings →
      Permissions → Connectors permissions**
  </Step>

  <Step title="Start a custom connector">
    Click **+ Custom connector** in the top-right corner, then select **Remote**
    in the modal.
  </Step>

  <Step title="Fill in the fields">
    | Field          | Value                                                          |
    | -------------- | -------------------------------------------------------------- |
    | Name           | `Rings`                                                        |
    | MCP Server URL | `https://production-api.joinrings.com/mcp`                     |
    | Description    | Relationship intelligence — people, companies, activity, deals |
    | Authentication | **OAuth**                                                      |
    | Transport      | **Streamable HTTP**                                            |

    Leave **Client ID** and **Client Secret** empty — Rings supports dynamic
    client registration and OAuth discovery, so Perplexity finds the endpoints
    and scopes itself.
  </Step>

  <Step title="Acknowledge and add">
    Tick the acknowledgement box, then click **Add**. The connector appears on
    the **Connectors** screen in your account settings.
  </Step>

  <Step title="Authenticate">
    Click the **Rings** connector card to start the sign-in flow and enable it.
  </Step>

  <Step title="Turn it on for a search">
    On the Perplexity home screen, enable **Rings** under **Sources**.
  </Step>
</Steps>

## Sharing it with your organization

Only admins can share a connector organization-wide. After creating it, the
creator opens **Enterprise settings → Permissions** and shares it there.
Organization members may not see it immediately.

For an org-wide connector using OAuth, an admin can either authenticate once on
behalf of everyone, or require each member to sign in with their own Rings
account. Per-member sign-in is the right choice for Rings, because tool results
are scoped to what each user can already see in the app.

## Editing or removing it

On the **Connectors** screen, click the ellipsis (⋮) on the Rings card and pick
the action you want.

<Tip>
  If the connector shows an error tag right after you add it, Perplexity's
  verification probe could not reach the server. Re-check the URL — it must be
  `https://` and end in `/mcp`.
</Tip>