Account Settings are viewable to any user with the Admin role. To access your company's account settings:
- Click on the Account tab on the left-hand navigation panel in the Portal.
- Select Company Settings.
- Here, you can view your company's account settings, categorized in 7 tabs:
-
- General
- Branding
- Mobile Apps
- Security
- Email Settings
- Data Delivery
- Recovery
-
The following tables outline the various account settings available in FastField:
General
| Setting | Description |
|---|---|
| Account Name | The name of your account. The name chosen must be unique across all FastField accounts. |
| Default Time Zone | The time zone that will be used when displaying date and time data. |
| Default Date Format | The format that will be used to display date and time values. |
| 24 Hour Clock | If checked, the 24-hour time (military time) format will be used to display time data. |
Branding
| Setting | Description |
|---|---|
| App Name | The name that can be used to replace FastField in branded emails and web confirmation screens. |
| Custom Logo | The logo image will replace the FastField logo in branded emails and web confirmation screens. The suggested dimension of this logo is 160px (w) x 40px (h). |
Mobile Apps
Toggle the switch icons to add and remove the following menu options on the Mobile App (the menu will be hidden if green):
| Setting | Description |
|---|---|
| Hide Forms Menu | This will hide the forms menu from the application interface |
| Hide Library Menu | This will hide the library menu from the application interface |
| Hide Inbox Menu | This will hide the inbox menu from the application interface |
| Hide Sync Menu | This will hide the sync menu from the application interface |
| Hide Submitted Menu | This will hide the submitted menu from the application interface |
| Hide Copy & Edit Form Menu | This will hide the copy & edit forms menu from the application interface |
| Hide Edit Form Menu | This will hide the edit forms menu from the application interface |
Security
This section allows you to configure your 2FA and SSO security measures.
| Setting | Description |
|---|---|
| Password Expiration in Days (0 = Never Expire) | Password Expiration in Days refers to the number of days after which a password will no longer be valid and the user will be required to create a new password. The number is typically set by an administrator and is used as a security measure to regularly update passwords and prevent unauthorized access to sensitive information. |
| Session Timeout in Minutes |
Session Timeout in Minutes refers to the length of time after which a user session will automatically end and the user will be required to log in again. This setting is used to maintain the security of sensitive information by automatically ending a session if the user is inactive for an extended period of time. The value of "Session Timeout in Minutes" determines the length of the inactive period before the session ends. For example, if the value is set to "30 minutes," the session will end after 30 minutes of inactivity and the user will need to log in again to continue using the system. |
| Allow users to configure 2FA |
2FA stands for Two-Factor Authentication, a security process that requires users to provide two separate authentication factors in order to access an account or system. To "configure 2FA" means to set up and activate the 2FA process on a system. This typically involves selecting and setting up a 2FA method, such as a one-time code generated by a smartphone app or a hardware token, and configuring the system to require the use of 2FA when logging in or accessing certain resources. The process may also involve assigning 2FA to specific users or user groups and setting 2FA policies for the system. The goal of 2FA is to provide an additional layer of security for sensitive information by requiring the user to prove their identity through multiple means, making it more difficult for unauthorized users to gain access. |
| Download our SSO Metadata file | Downloading the SSO metadata file is typically the first step in integrating an application with an SSO system. The metadata file is used by the application to establish a secure connection with the SSO system, allowing users to log in to the application using their SSO credentials. The file can be downloaded from the SSO service provider's website or from a secure location within the SSO system. |
| Upload your SSO Metadata file | Uploading an SSO file involves sending the file from a local device or network location to a remote server or system, where it can be processed and used to configure the system to work with the SSO system. This step is typically performed by an administrator or technical user with the appropriate permissions. Once the file is uploaded and processed, the system should be configured to use the SSO system for authentication and allow users to log in using their SSO credentials. |
| SSO Organization Code | An SSO Organization Code, or Single Sign-On Organization Code, is a unique identifier assigned to an organization within a Single Sign-On (SSO) system. |
| SSO URL | The SSO URL is a critical component of an SSO system and is used by all connected systems to communicate with the SSO service. The URL may be publicly accessible or restricted to specific users or networks. |
Email Settings
Note: Email template content can be previewed by clicking on the Preview button at the top of each HTML editor.
| Setting | Description |
|---|---|
| Form Submission Email Recipients | |
| Form Submission Email Subject | The email subject will be sent to all users who have subscribed to form submission notifications. These notifications are sent upon receipt of new form submissions by FastField. |
| Form Submission Email Body | The body of the email will be sent to all users who have subscribed to form submission notifications. These notifications are sent upon receipt of new form submissions by FastField. |
| Form Dispatch Email Subject | The subject of the email that will be sent to form dispatch recipients. |
| Form Dispatch Email Body | The body of the email that will be sent to form dispatch recipients. |
| Reply-To Email | The email address will be set in the From field of emails sent via FastField. |
| Custom From Email Address | Allows you to use a custom From email address, but requires that you own the domain used and that you can add entries in your host's DNS section. |
| Email Footer | The footer content will be applied to all branded email content sent via FastField. |
| Account Creation Email Subject | The email subject will be sent to a prospective user when their new account is created in FastField. |
| Account Creation Email Body | The email body that will be sent to a prospective user when their new account is created in FastField. This body content will be appended to the boilerplate email confirmation content that directs the user to confirm their FastField account. |
| Anonymous Dispatch Email Subject | |
| Anonymous Dispatch Email Body |
Recovery
Data Delivery
| Setting | Description |
|---|---|
| Destination | Indicates how the submitted form data should be handled upon receipt by FastField. Options include Vault (Default), FTP, SFTP, and Email. See Destination Types for descriptions of each type. |
| Format | Indicates what format the submitted form data should be processed into upon receipt by FastField. Options include JSON (Default), Excel, XML, Prophet and CSV. See Format Types for descriptions of each type. |
Destination Types
| Setting | Description |
|---|---|
| Vault (Default) |
This is the default destination. When chosen, all forms will be stored in the FastField data vault. Note: When choosing this destination type, form submission data can only be processed in JSON format. |
| FTP | Use this destination to send form submissions to your FTP server. |
| SFTP |
Use this destination to send form submissions to your SFTP server. Note: When choosing this destination type, your server must be set up to use the SSH File Transfer Protocol. |
| Use this destination to have form submissions sent to your email address. | |
| HttpPost |
Also known as Direct Post, use this destination to have form submissions sent to your HTTP REST service endpoint that accepts JSON form submission data POSTed directly from the FastField apps. See the Form Submissions to Custom Endpoint section for details. Note: When choosing this destination type, form submission data can only be processed in JSON format. |
Format Types
| Setting | Description |
|---|---|
| JSON (Default) | This is the default format. When chosen, all forms will be sent in JSON format. |
| Excel* | Use this format to send form submission data in Excel format. When form submission data is sent in Excel format, Subforms and multi-photo data will be included in separate Worksheets in the same Workbook (file) as the root data. See Form Submission Format Types](#FormSubmissionFormatTypes) |
| CSV* |
Use this format to send form submissions in CSV format. Note: When form submission data is sent in CSV format, no Subform or multi-photo data will be sent, so avoid using these on your forms if you choose to use CSV format. |
| XML | Use this format to send form submissions in XML format. |
| Prophet | Use this format to send data in the Prophet platform required format. |
*If you choose Excel or CSV as the Form Submission Format type, you will also be able to choose if the resulting file should use field keys instead of field names for the column headers.
Other Related Integration Settings
FTP/SFTP Submission Destination Settings:
| Setting | Description |
|---|---|
| FTP Host | The hostname of the FTP where forms submissions will be transferred to when FTP or SFTP is used as the integration destination. |
| FTP User | The user name of an authorized FTP user will be used to authenticate when FTP or SFTP is used as the integration destination. |
| FTP Password | The password of an authorized FTP user will be used to authenticate when FTP or SFTP is used as the integration destination. |
| Use SSH Key for SFTP Auth | If checked, an SSH key will be used instead of a password to authenticate when FTP or SFTP is used as the integration destination. When using this option, contact FastField support to obtain the SSH key that you will need to associate with the FTP user FastField will authenticate with. |
| FTP Directory Path | An optional directory path where submission data will be sent to when FTP or SFTP is used as the integration destination. |
Email Submission Destination Settings:
| Setting | Description |
|---|---|
| Integration Email Recipient |
One or more email addresses where form submissions will be emailed to when Email is set as the integration destination. Note: Separate multiple email addresses with commas. |
| Integration Email From Address | The body of the email that is sent when Email is set as the integration destination. |
| Integration Email Subject | The subject of the email that is sent when Email is set as the integration destination. |
| Integration Email Body | The body of the email that is sent when Email is set as the integration destination. |