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

# ShareFile

> Connect ShareFile to Oleria to bring employees, external clients, groups, roles, connected apps, and activity from your file sharing platform into your identity and access graph.

ShareFile is a secure file sharing and transfer platform. Connect your ShareFile account to Oleria to see who has access to it: employees, external clients, their roles and groups, and the third-party apps they've authorized. Oleria reads this data from the ShareFile API using an OAuth API key that you create, so you can find dormant or over-privileged accounts and take action directly from Oleria.

## What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from your ShareFile account:

* **Accounts** - every employee user and every external client user, with their name, email address, status, and last sign-in. Employee accounts also show whether two-step verification or single sign-on applies to them.
* **Groups** - every shared distribution group and its members. Oleria also maps ShareFile's built-in Super Users group.
* **Roles** - the ShareFile permissions held by each employee. Oleria shows each permission as a role under its ShareFile API name, for example `AdminManageEmployees` for **Manage Employees** and `AdminReporting` for **Access reporting**.
* **Connected apps** - third-party apps that employees have authorized to access ShareFile. Oleria shows each app as a non-human identity, with the employees who authorized it as its owners.
* **Activity** - sign-ins, failed sign-ins, two-step verification events, and file activity such as uploads, downloads, views, moves, and deletes. Oleria also imports access changes, such as permission changes and users added to groups.

<Note>
  Oleria doesn't map ShareFile folders, folder permissions, or share links.
</Note>

<Note>
  To read activity, Oleria creates reports in ShareFile with names that start with `oleria-`, and deletes them after each sync. You might see these reports briefly under **Reports** in ShareFile.
</Note>

## Prerequisites

* A ShareFile administrator account. The admin who approves access must be the master admin, or an employee with the **Manage Employees** and **Access reporting** permissions. To add or remove group members from Oleria, the admin also needs **Edit other users' shared distribution groups**.
* Admin access to the Oleria workspace.

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

## Create an API key in ShareFile

<Steps>
  <Step title="Open the API key page">
    Go to [api.sharefile.com/apikeys](https://api.sharefile.com/apikeys) and sign in with your ShareFile admin account.
  </Step>

  <Step title="Create an API key">
    Create a new API key and give it a name, for example `Oleria Integration`. Set the redirect URI to your Oleria workspace URL followed by `/workspace/integrations/sharefile/connect`, for example `https://acme.oleria.io/workspace/integrations/sharefile/connect`.

    <Note>
      Use the Oleria URL from your browser's address bar. The redirect URI must match exactly, or ShareFile rejects the sign-in.
    </Note>
  </Step>

  <Step title="Copy the client ID and client secret">
    Copy the **Client ID** and **Client Secret** for the new API key. You'll paste them into Oleria in the next section. Store the client secret securely.
  </Step>
</Steps>

## Connect ShareFile to Oleria

<Steps>
  <Step title="Open the integration">
    Go to your Oleria workspace, select **Integrations** -> select **ShareFile**.
  </Step>

  <Step title="Complete the connection form">
    Select **Continue** and provide the following:

    | Field | Notes |
    | :- | :- |
    | ShareFile Domain | Required. The domain you sign in to ShareFile at, for example `acme.sharefile.com` or `acme.sharefile.eu`. |
    | OAuth Client ID | Required. The client ID of the API key you created. |
    | OAuth Client Secret | Required when you first connect. The client secret of the same API key. |
  </Step>

  <Step title="Approve access in ShareFile">
    Select **Authenticate**. ShareFile asks you to sign in and approve access. Sign in as a ShareFile administrator and approve the request.

    Oleria then checks that the approving user is the master admin, or holds the **Manage Employees** and **Access reporting** permissions. If not, the connection fails.
  </Step>
</Steps>

## Verify the integration

Confirm the ShareFile account appears on the **Connected** tab of your Oleria **Integrations** page. After the first sync completes, you can review the discovered accounts, groups, roles, connected apps, and activity in your Oleria workspace.

<Note>
  Oleria reads ShareFile as the user who approved access. If that user is disabled or loses their admin permissions, edit the integration and select **Update**, then approve access in ShareFile as another administrator. Leave **OAuth Client Secret** blank to keep the saved secret.
</Note>

## Remediation actions

Oleria can take the following actions in ShareFile. Each action requires the user who approved access to hold the listed permission, or to be the master admin:

| Action | Required ShareFile permission |
| :- | :- |
| Disable or re-enable a user | **Manage Employees** |
| Add or remove a user from a group | **Edit other users' shared distribution groups** |
| Grant or remove a role | **Manage Employees** |
| Revoke a connected app's access | Master admin only |

Revoking a connected app removes the app's access for every employee who authorized it. Oleria can't undo this action; each employee must authorize the app again.

To protect your account, Oleria doesn't:

* Disable the ShareFile user who approved access for Oleria, or remove the `AdminManageEmployees`, `AdminReporting`, or `AdminSharedDistGroups` role from them (unless they're the master admin).
* Grant or remove the `MasterAdmin` or `Employee` role.
* Change Super Users membership as a group. Grant or remove the `SuperUser` role instead.
* Revoke the API key Oleria uses. It appears under connected apps with the name you gave it in ShareFile.

## Contact us

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


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.