Users
The Users API allows you to manage user accounts within your Files.com site.
User Permissions
ExaVault permissions differ from the permissions available on Files.com, so interacting with user permissions through the ExaVault Legacy APIs requires some translation.
Some ExaVault permissions, such as notification, viewFormData, deleteFormData, and undelete, are meaningless on Files.com. Other ExaVault permissions, such as modify and delete, are contained within other Files.com permissions.
Some combinations of permissions are no longer supported. For example, you cannot create a user who has upload but not list permissions, so assigning a user upload permissions via the legacy ExaVault API also grants list permissions.
How ExaVault Permissions Map to Files.com Permissions
When you provide permissions for endpoints that create or modify users, the resulting user in your Files.com site may have permissions you did not expect. This is mostly due to the difference in how the platforms handle the ability for users to delete or overwrite files.
When you create or update a user with a combination of legacy permissions, the result is the union of the resulting permissions in Files.com.
| Granted Legacy Permission | Resulting User Permissions in Files.com |
|---|---|
list | list |
download | read + list |
upload | full + write + read + list |
modify | full + write + read + list |
delete | full + write + read + list |
share | list + read + share |
changePassword | None granted. This is a user setting for whether the user can change their password. |
notification, viewFormData, deleteFormData, undelete | None granted. This is not a separate permission in Files.com. |
How Files.com Permissions Map to ExaVault Permissions
As described above, the permission information returned by the legacy ExaVault API requires some interpretation.
We do not recommend using the legacy ExaVault APIs to audit your user permissions within Files.com. Instead, use one of the Files.com SDKs, which returns information consistent with the actual user permissions.
| Files.com Permissions Assigned to User | Returned ExaVault User Permission |
|---|---|
admin (includes full, write, read, list, share, history) | download, upload, modify, delete, list, share, notification, viewFormData, deleteFormData |
full (includes write, read, list) | download, upload, modify, delete, list, notification |
read/write (includes list) | download, upload |
read (includes list) | download, notification |
write (includes list`) | upload |
share (includes read, list) | download, list, share |
history (includes list) | none |
ExaVault Home Directories versus Files.com Path Permissions
The ExaVault platform supported assigning only a single home directory for a user, and all permissions were granted recursively within that path. The legacy ExaVault API can only support a single path for a user's permissions.
If you have granted your users permission to multiple paths within Files.com, the legacy ExaVault API may return unexpected results.
Get The File Orchestration Platform Today
4,000+ organizations trust Files.com for mission-critical file operations. Start your free trial now and build your first flow in 60 seconds.
No credit card required • 7-day free trial • Setup in minutes