Skip to main content
Connect Files.com to Oleria to see who has access to your Files.com site and its folders. Oleria reads identity and access data from the Files.com API with an API key, so you can find over-privileged accounts and unused keys, and take action directly from Oleria.

What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from your Files.com site:
  • Accounts - every user, with their name, email address, status, last login, last password change, two-factor authentication, and single sign-on settings. Partner users appear as external accounts.
  • Non-human identities - Shared/Bot users, API keys, and SFTP/SSH keys, linked to the user that owns them, with expiration and last-used dates where Files.com records them.
  • Credentials - API keys, SFTP/SSH keys, secrets in the Files.com Secret Store, and saved remote server credentials. Oleria imports details such as names and dates, never the secret values.
  • Roles - Files.com’s admin levels: Site Administrator, Read-only Site Administrator, Workspace Administrator, Partner Administrator, Billing Administrator, Group Administrator, and Folder Administrator. Files.com has no custom roles, so Oleria derives these from each user’s settings and folder permissions.
  • User groups - groups and partners, with their members. Group administrators are marked as the group’s managers.
  • Folders and access - folders that have their own permissions, and who can reach them: users, groups, partners, and people with a share link. Folder administrators are marked as the folder’s managers.
  • Activity - the action log, SSO and user security events, API requests, and settings changes. How far back Files.com keeps this depends on your plan.
Oleria refreshes this data on its regular sync schedule.
Oleria imports folders that have their own permissions, plus the site root. A folder without its own permissions inherits access from its parent folder, so Oleria doesn’t import it separately.

Prerequisites

  • A Files.com user with the Site Administrator role, to create the Oleria user and its API key.
  • Admin access to the Oleria workspace.
Create a dedicated Files.com user for Oleria and create the API key on that user. An API key has no scopes of its own and acts with the role of the user it belongs to, so the connection stops working if that user is disabled or loses its role. Don’t use a Shared/Bot user: its keys can’t read other users’ API keys or administer the site.

Create an API key in Files.com

1

Create a user for Oleria

Sign in to Files.com as a Site Administrator. Go to Users & Groups > Users, select New User, and give the user the Read-only Site Administrator permission. To use remediation actions with the same key, select Site Administrator instead.
2

Open API keys

Go to Clients & Protocols > SDKs and API > API Keys, then select New API Key.
3

Create the key

Enter a name such as Oleria Integration, set Permission Set to Full Access, and select the Oleria user as the key’s User. Optionally, set a Valid Through date. Select Save. Files.com asks for your password to confirm.
4

Copy the key

Copy the key somewhere secure.
Files.com shows the key only once. If you lose it, create a new key and update the integration in Oleria.
5

Optional: create a remediation key

To let Oleria take actions with a separate key, repeat these steps for a user with the Site Administrator role. Use this key as the Remediation API key in the next section.
Files.com documents some data as available only to Site Administrators. If API keys, SFTP/SSH keys, secrets, or activity don’t appear in Oleria with a Read-only Site Administrator key, use a key that belongs to a Site Administrator.

Connect Files.com to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations -> select Files.com.
2

Complete the connection form

Provide the following:
3

Confirm the connection

Select Authenticate to validate the keys. Oleria rejects a key that doesn’t have the Full Access permission set, that belongs to a Shared/Bot user, or whose user isn’t a Read-only Site Administrator or Site Administrator. The Remediation API key must belong to a Site Administrator.

Verify the integration

Confirm your Files.com site appears on the Connected tab of your Oleria Integrations page with a status of Healthy. After the first sync completes, you can review the discovered accounts, groups, roles, folders, and keys in your Oleria workspace.
If you replace or delete the API key in Files.com, edit the integration in Oleria and enter the new key. An expired or deleted key causes the sync to fail. To keep the existing key when you edit other settings, leave the key field empty.

Remediation actions

Oleria can take these actions in Files.com. Each one runs with the Remediation API key, or with the API key if you didn’t add one. That key must belong to a Site Administrator.
  • Disable a user and re-enable a user.
  • Create a user and delete a user. Oleria never sets a password for a new user. Deleting a user can’t be undone.
  • Create a group.
  • Add a user to a group and remove a user from a group.
  • Grant or remove an admin role: Site Administrator and Read-only Site Administrator. Oleria can remove the Group Administrator role but can’t grant it.
  • Revoke a user’s folder permission, and remove a partner user’s access to a folder.
  • Revoke share links on a folder, both public links and links shared with specific people. Oleria sets the link to expire, so you can restore it.
  • Disable a non-human identity: Oleria disables a Shared/Bot user, or sets an API key to expire. Files.com has no way to disable an SFTP/SSH key, so Oleria deletes it, and that can’t be undone.
Keep these limits in mind:
  • Oleria won’t disable, delete, demote, or remove access from the users that the integration’s keys belong to, or from your site’s main administrator. It also won’t disable their API keys or SFTP/SSH keys. Doing so would disconnect the integration or lock you out.
  • Revoking a folder permission removes only the user’s own permissions on that folder. If the user reaches the folder through a group or partner, Oleria refuses the action: remove the user from the group, or change the group’s permission, in Files.com.
  • Oleria refuses to revoke a user’s permission that applies to the folder only because it’s set recursively on a parent folder, since removing it would also remove access to every other folder below that parent. Revoke it on the parent folder instead.
  • Removing a partner user’s access applies to one folder, or to every folder if you don’t choose one. The same group and partner refusal applies.
  • Removing the Group Administrator role removes it from every group the user administers.
  • Granting Read-only Site Administrator to a user who is already a Site Administrator is refused. Remove Site Administrator first.
  • A new user is created disabled unless you choose to activate them.
  • Re-enabling a user whose access expired or whom a lifecycle rule made inactive is refused. Change the expiration date or lifecycle rule in Files.com instead.

Known limitations

  • Oleria connects to sites on a files.com subdomain. Sites that you reach only through a custom domain aren’t supported.
  • Files.com groups can’t contain other groups, so there are no nested groups to import.
  • Files.com has no custom roles. Oleria imports the built-in admin levels only.
  • How far back activity goes depends on your Files.com plan. The action log covers up to six months.
  • If you connected Files.com with a SCIM token before this integration was released, that connection stops syncing when the new integration is enabled. Delete it and create a new one with an API key as described above. The old connection can’t be edited into the new one.

Contact us

For questions about this integration, contact us at support@oleria.com.