Creating Users offers a few different methods of creating a user. Site Administrators can use the Web to create a single user or use the Bulk import users feature to save time when creating multiple users. Additionally, we also offer the ability to Clone a user, and create user groups to help with onboarding additional users. You can also automate user creation using the API/SDKs or our CLI application. User accounts can be manually created on the Users page of the web portal.

New user creation allows you to select authentication methods, group memberships, as well as folder permissions on selected folders for the user. Advanced settings are available while creating users. Using these settings you can setup additional configurations and permissions for the user including Admin permissions, IP restrictions, shared/bot user config, allowed protocols to be used, SSH (SFTP) keys, and an expiration date. also offers seamless user provisioning and de-provisioning through the use of SCIM (System for Cross-domain Identity Management) and LDAP (Lightweight Directory Access Protocol). With SCIM, the process of creating and managing user accounts becomes automated, ensuring efficient and consistent user onboarding by using your existing identity provider. LDAP integration provides a reliable method for accessing and maintaining directory services, making it easier to synchronize and manage user data.

Cloning Users

Administrators can save time when creating a new user by cloning an existing user. This speeds up the user creation process by pre-populating most of the user's settings from the user being cloned, including group membership and permissions.

Bulk Import

You can create or import users in bulk via the web portal interface using our Bulk Create option.

On the Users page, click the Bulk Create button, then expand the Supported columns legend to review the data options you can include in your import file.

You can use the Download CSV template button for an example CSV file which you can modify and use for your import.

Once you have your CSV file populated according to the template and legend, use the Choose File button to select the CSV file from your local file system and then begin the import process.

The system will validate your file and show you any data errors that need to be corrected before your user import can be processed.

usernameThe login name for the new userRequired - Can be any text
authentication_methodHow the user's credentials are created.password (default), password_with_imported_hash, email_signup, password_and_ssh_key, or any enabled SSO provider
passwordThe new user's password. Only valid if the authentication_method is passwordAny text that matches your site's password rules
password_validity_daysHow many days a password is valid before the user is required to change it. This overrides the site-wide setting.Any whole number or 0. Can also be blank if not overriding the site-wide setting
require_password_changeShould the user be forced to change their password when the log in the first time?Y or N
emailThe user's email address. Required if authentication_method is email_signupA valid email address
full_nameThe user's full name.Text containing at least 2 words separated by a space
companyThe name of the user's associated companyAny text
group_idsWhich groups this user is a member ofComma-separated list of groups. Can be any combination of group names or numeric group IDs.
site_adminIs this user an administrator (who has full access to the entire site and its settings)?Y or N
self_managedDoes this user manage its own credentials (i.e., is NOT a bot/shared user)?Y or N. Can only be Y if authentication_method is email_signup
notesAny notes about this user. Will be visible to all site admins on the users page.Any text
time_zoneWhat time zone the user is inThe time zone name
root_folderRoot folder for FTP (and optionally SFTP if the appropriate site-wide setting is set.) Note that this is not used for API, Desktop, or Web interface.
Text containing a valid path to a folder the user has permission to access, e.g. "Customers/ACME" or "Sales". Does not need leading or trailing slashes.
When a user with a root folder logs in via FTP and the path does not exist (because it has been deleted), it will be automatically created, but the user will not have permissions to the folder.
ip_whitelistA list of IP addresses the user is allowed to connect from.Text containing the IP addresses in CIDR format, separated by newline (\n) characters. You may specify a range in CIDR format, such as Example: "\n13.211.6.58\n192.168.17.0/27"
enforce_ip_whitelistShould this user be required to connect from a site-allowed IP address? If Y, then the "Bypass site IP whitelist" setting for the user will be disabled. If N, then the "Bypass site IP whitelist" setting will be enabled. If the user has their own ip_whitelist configured (see above), that list will still be valid even if this field is set to N.Y or N
ssl_requiredWhether the user is required to use TLS or SSL when connecting via FTP. If this is set to Y, the user cannot connect with an unencrypted FTP connection.Y or N. If left blank, will use the site-wide setting.
access_expiration_dateScheduled Date/Time at which user will be deactivatedText containing a date in ISO 8601 format (YYYY-mm-ddTHH:MM:SS followed by offset from UTC) Example: 2020-03-14T13:27:01-04:00
ftp_permissionWhether the user is permitted to connect via FTP or FTPSY or N
sftp_permissionWhether user can connect via SFTPY or N
dav_permissionWhether user can connect via WebDAV?Y or N
restapi_permissionWhether user can connect via the web UI, Desktop App, or the REST API?Y or N
folder_permissionsPermissions to automatically assign to new usersText containing a list of folders and permissions, separated by pipe symbols (|), to assign to the newly created user.

Bulk Create with Folder Permissions

Automatically assign folder permissions to users with the folder_permissions column of the import file. Supply a list of folders and permissions, separated by pipe symbols, to be assigned to the user.

Possible Permission Values

  • admin : Able to manage settings for the folder.
  • full : Able to read, write, move, delete, and rename files and folders.
  • readonly : Able to list and download files and folders.
  • writeonly : Able to upload files and create folders.
  • readwrite : Shorthand for readonly,writeonly
  • list : Able to list files and folders, but not download.
  • bundle : Able to share files and folders via a share link.
  • history : Able to view the history of files and folders.



This defines 3 permissions: Sales=readonly, Engineering=readwrite,history and Home/Adam=admin. The user will be given Read-Only permission on the /Sales folder, Read/Write and History permissions on the /Engineering folder, and Admin permission on the /Home/Adam folder. If any of those folders do not exist, they will be created automatically.

Advanced Usage Notes

Use a slash for the folder name to specify the Root Folder, for example: /=readonly. If a folder name contains a vertical bar, for example Sales|North-America, the vertical bar must be escaped with a preceding backslash: Sales\|North-America=readonly.

If site_admin is enabled for the user, then the value of folder_permissions is ignored, because site administrators have admin access to all folders.

Permissions are applied recursively to all sub-folders. To limit a permission to the specified folder name and not its sub-folders, add an asterisk * after the permission value. For example: Home=admin*

Get Instant Access to

The button below will take you to our Free Trial signup page. Click on the white "Start My Free Trial" button, then fill out the short form on the next page. Your account will be activated instantly. You can dive in and start yourself or let us help. The choice is yours.

Start My Free Trial

©2024 All right reserved


  • Start My Free Trial
  • Pricing
  • Docs
  • API and SDKs
  • Contact


(800) 286-8372


9am–8pm Eastern