> ## 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.

# Druva

> Connect your Druva account to Oleria to continuously discover user access across your cloud data protection platform.

Druva is a cloud data protection and backup platform. Connect your Druva account to Oleria to bring user access into your identity and access graph, without a dedicated Druva-specific integration.

## What Oleria discovers

User accounts and profile attributes synced from Druva's directory. Oleria uses this data for dormant account detection and access reviews, refreshed on Druva's standard sync schedule.

## Prerequisites

* Admin access in Druva with permission to create an API credential.
* 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 Druva's own API documentation.
</Note>

## Get your SCIM credentials from Druva

<Steps>
  <Step title="Create an API credential in Druva">
    Sign in to Druva as an admin and go to **Governance** → **API Credentials** to create a credential for machine access.
  </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 Druva account.
    * **Authentication token** - the API credential you created.

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

## Connect Druva to Oleria

<Steps>
  <Step title="Open the integration">
    Go to your Oleria workspace, select **Integrations**, then select the **Druva** 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, `druva-prod`). |
    | SCIM Base URL        | Required. The HTTPS API endpoint copied from Druva.                                  |
    | Authentication token | Required. The API credential issued by Druva.                                        |
  </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 from Druva on the standard SCIM provisioning schedule once the initial sync completes.

<Note>
  If Druva rotates your API credential, update the Authentication token in Oleria by editing the integration.
</Note>

## Governance actions

Oleria can also invoke lifecycle actions in Druva when the credential you provide has write access:

* Enable or disable a user account
* Create a new user

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

## Contact us

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