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

# New Relic

> Connect your New Relic account to Oleria to continuously discover user and group access across your observability platform.

New Relic is an observability platform for monitoring applications and infrastructure. Connect your New Relic account to Oleria to bring user and group access into your identity and access graph, without a dedicated New Relic-specific integration.

## What Oleria discovers

* User accounts and profile attributes synced from New Relic's account directory.
* Groups and their memberships.

Oleria uses this data for dormant account detection and access reviews, refreshed on New Relic's standard sync schedule.

## Prerequisites

* Admin access in New Relic with permission to create a user API key.
* Admin access on the Oleria platform to add a new integration.

<Note>
  The exact location of these settings can change over time. If the steps below don't match what you see, refer to New Relic's own API documentation.
</Note>

## Get your SCIM credentials from New Relic

<Steps>
  <Step title="Create a user API key in New Relic">
    Sign in to New Relic as an admin, go to **Administration** → **API Keys**, and create a user API key.
  </Step>

  <Step title="Copy your SCIM Base URL and Authentication token">
    Copy both values before you leave the page - you'll paste them into Oleria in the next section:

    * **SCIM Base URL** - the HTTPS API endpoint for your New Relic account.
    * **Authentication token** - the API key you generated.

    <Note>
      Copy the key now. Many applications display it only once. Store it securely and rotate it per your organization's security policy.
    </Note>
  </Step>
</Steps>

## Connect New Relic to Oleria

<Steps>
  <Step title="Open the integration">
    Go to your Oleria workspace, select **Integrations**, then select the **New Relic** tile.
  </Step>

  <Step title="Complete the connection form">
    Select **Continue** and fill in the connection form:

    | Field                | Notes                                                                                    |
    | :------------------- | :--------------------------------------------------------------------------------------- |
    | Instance name        | Optional. Short, recognizable label for this connection (for example, `new-relic-prod`). |
    | SCIM Base URL        | Required. The HTTPS API endpoint copied from New Relic.                                  |
    | Authentication token | Required. The API key issued by New Relic.                                               |
  </Step>

  <Step title="Save the integration">
    Select **Connect** to validate the credentials and save the integration.
  </Step>
</Steps>

## Verify the integration

Confirm the new instance appears in your Oleria workspace under **Connected Integrations** with a status of **Healthy**. Oleria syncs users and groups from New Relic on the standard SCIM provisioning schedule once the initial sync completes.

<Note>
  If New Relic rotates your API key, update the Authentication token in Oleria by editing the integration.
</Note>

## Governance actions

Oleria can also invoke lifecycle actions in New Relic when the key you provide has write access:

* Enable or disable a user account
* Add or remove a user from a group
* Create a new user or group

<Note>
  Many teams start with a read-only key for visibility, then grant write access once they're ready to automate remediation in New Relic.
</Note>

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).