Restricting a User's Protocol Privileges
Each user can be restricted to a specific set of data transmission protocols for connecting to Files.com. Controlling which protocols a user account can use helps you meet the security compliance regulations that apply to your business or industry.
Use the Protocol Access setting, within the user account's Privileges settings, to allow or disallow the selected user's access to FTP (including FTPS and FTPES), SFTP, WebDAV, Web Portal, Desktop App, and the Files.com API.
| Protocol Setting | API Attribute | Description |
|---|---|---|
| FTP | ftp_permission | Specifies whether the user account is allowed to connect using the FTP, FTPS or FTPES protocol. |
| SFTP | sftp_permission | Specifies whether the user account is allowed to connect using SFTP protocol. |
| WebDAV | dav_permission | Specifies whether the user account is allowed to connect using WebDAV or WebDAVS protocol. |
| Web, Desktop App, and API | restapi_permission | Specifies whether the user account is allowed to connect using the Files.com web portal, the Desktop App, or via the REST APIs using the HTTPS protocol. |
User accounts with Administrator access privileges cannot be denied access to the Web Portal, Desktop App, and the Files.com API, but they can be denied access to FTP (including FTPS and FTPES), SFTP, and WebDAV.
This setting works in conjunction with the user's IP Whitelist setting and the user's Access Control by Country setting.
Group Protocol Access vs User Protocol Access
By default, protocol access can be assigned either through users or through groups. A user can connect with a protocol if it has been enabled for their user account, or if they are a member of a group with that protocol enabled.
You can configure your site to manage all protocol access through groups. When you enable this setting, only users who are members of groups with a protocol enabled can use that protocol to connect. Protocol access for individual users is ignored, and only the group settings take effect.