Company Settings

Security

When you go to the Home > Company > Company Settings menu command, the Company Settings window opens at the Security tab - .

Figure 1 - The Company Settings > Security tab

The options are as follows:

• Always use SSL in surveys - Check this box to generate all links to limited surveys as secure links, for example https://survey.yourserver.com/wix/pXXXXXX.aspx. The Respondents > Emailing > Secure option will then be chosen by default and locked to prevent changes.
• Always use SSL in Authoring and Reportal - Check this option to force all users in this company to use the https:// link for authoring and Reportal access.
• Always use encrypted file transfer - Check this box to encrypt all data exports, report exports and respondent exports. The setting forces all exports and imports that support encryption to be encrypted. The system cannot prevent the user uploading plain text data files to the client as the encryption is not checked until the import task is actually run, so unencrypted files can lie on the server. However any import tasks will fail if the data file is not encrypted. Note that when the box is checked, to be able to upload respondents for the users in this company, the respondent list must also be encrypted.

Note: PGP enforcement does not apply to end user downloads - the export data permission allows unencrypted downloads to end users.

• Always use FTP for file transfer - Check this option to make FTP the only option available in the “File transfer” field on the set up page for data exports, report exports and respondent export. The Email option will not then be available. Data imports and survey import and export are not affected by this setting and do not have to be to/from an FTP server.
• Always use FTP for data exports - check this option to make FTP the only option available in the “File transfer” field on the set up page for data and respondent exports. The Email option will not then be available. Survey import and export are not affected by this setting and do not have to be to/from a FTP server.
• Enforce SFTP (SSH for FTP) - Check this option to enforce SSH when using FTP for importing/exporting data.
• Enforce db encryption - If the Database Encryption add-on is licensed by your company, then this option will be available. Check this option to enforce encryption for all new databases created for surveys. Note that this is not retro-active and will only apply to new databases. If you want the databases to be encrypted for existing company surveys, the surveys must be re-launched and new databases must be created. Encryption only applies to the production survey database; system databases and multimode databases are not encrypted.
• Restrict data export tasks... - If this option is checked, only users registered to the same company as the survey owner will be able to perform exports on this customer's surveys. Even users with system_admin or company_admin permission will not be able to perform exports if they are not registered with the survey owner's company. An account administrator or system administration can edit this setting under the Admin > Accounts > Companies menu. Note that any changes to this property are registered in the system activity log.
• Disable the ability to change email-address when exporting data - check this option to prevent access to the email address field when exporting data. This is intended to reduce the risk that someone accidentally changes this field and thereby sends confidential information to someone who should not receive it. Note that the Override button is still available, however this must then be used with intent so is a more thought-through process.
• Prevent most Saas... - Check this option to prevent users with SYSTEM_PROJECT_ADMINISTRATE from implicitly being granted access to projects (surveys, polls and panels) in this company. Any user can still gain access to the project, but only if they are explicitly granted permission to do so. Users with SYSTEM_ADMINISTRATE can access all projects irrespective of this setting.
• Enable survey db level auditing - check this option to enable SQL Server auditing at the survey database level. When enabled, all surveys created for this company will have database auditing enabled. This audit log is not accessible through the Authoring user interface.
• Pwned passwords threshold - specify the maximum number of times a new password can be found in previous data breaches before it will not be accepted. The recommended setting is 0, which means that if the chosen password appears in the list of breached passwords then it will not be accepted. A blank value disables the restriction. The pwned password service of haveibeenpwned.com is queried. Note that to maintain security only the first 5 HEX characters of an SHA-1 hashed password are sent.
• Company AES key value- If Single Sign-on or External Respondent Limited Surveys are to be used, an AES key is required. The key assigned can be viewed here. When this value is defined it allows the survey setting to be selected by users; when not defined it is grayed out.
• Cint API Key - The Cint API key is required if you wish to allow the survey scripting function to pass transition information over to Cint using their Server-to-Server (S2S) encryption.

• Lucid hash encryption key - The Lucid SHA1 hash encryption key (provided by Lucid) should be pasted here to ensure that the system-generated URL which is used to transition information sent to Lucid is encrypted and not passed as plain text.

Survey Channels

To access the options on the Survey Channels tab, go to the Home > Company > Company Settings menu command and select Survey Channels. The tab opens as shown below - .

Figure 2 - The Company Settings > Survey Channels tab

The options are as follows:

• Override sitewide domain in survey URLs - if you are running surveys for customers, the customers may not wish the links to their surveys to include another domain name, for example ....Forsta.com. Your company may therefore set up a permanent domain override as a company-wide default setting. If you wish to use a domain other than the default in the survey links, select the "Override site-wide domain in survey URLs" checkbox and specify the new domain in the field below. You must first register the domain you wish to use (if not already done) and set up a domain record to point towards the public IP address of the interviewing server(s) in the DNS domain manager.
• Override sitewide domain in short URLs - [The Short URLs functionality is an add-on. Contact Forsta Support for details]. If you wish to use a domain name other than the default in short URLs for surveys, you may set up a permanent domain override as a company-wide default setting. You must first register the domain you wish to use (if not already done) and set up a domain record to point towards the public IP address of the interviewing server(s) in the DNS domain manager. Once the domain is set up, select the “Override sitewide domain in short URLs” checkbox and specify the new domain in the field below.

Important:
When typing the domain link into the field for either of the above properties, ensure you do not include a trailing space (a space character at the end of the domain). A trailing space in this link will give an error during launch for all surveys, preventing any surveys from being launched by the company.

• Enduser List ID - The CAPI/Kiosk Interviewers must be created in an End User List. The ID of this End User List must be registered in the Enduser list ID field. Only one CAPI/Kiosk Interviewer End User list can be registered. Refer to the CAPI/Kiosk documentation for further details.
• Company Alias - The CATI interviewer must log in using his/her username and password and also a company name as part of the identification. This will be the alias specified for this company, and the field cannot be empty.

Branding

This tab - contains a number of settings and fields that allow you to set your own company branding onto the Reportal login page. All panelists and end users for your company will then see this custom login page.

Figure 3 - The Company Settings > Branding tab

• Tile background - enter the URL path to an image uploaded to the file library. This image will then be used as the tiled background image of the underlying page area. Note that only images hosted in the file library can be used.
• Background image - enter the URL path to an image uploaded to the file library. This image will then be used as the background image of the login details area. Note that only images hosted in the file library can be used.
• Text color - sets the color of the text used in the login page. Either type the color code number into the field, or double-click on the example square to open a color picker and select the color you wish to use.
• Button image - enter the URL path to an image uploaded to the file library. This image will then be used as the Submit button image on the login page. Note that only images hosted in the file library can be used.
• Preview - enables you to check the page before you save the changes.
• Disable Confirmit Branding - check this box to remove all references to Confirmit for Reportal users, specifically:
• The Forsta logo in the top right of the Report list page.
• The Forsta copyright text in the bottom right corner.
• Mentions of Forsta in Reportal export emails.
• Disable cookie information - check this box to remove the standard "Cookie" text from the Reportal log-in page. This text informs users that Forsta Reportal uses cookies. Whilst removing this text may be desirable for your branding purposes, read the Important note below first.
• Report logo - you can add a logo to the upper-right corner of the Instant Analytics report page (go to About Instant Analytics for more information). Add the URL to your logo file into the Report Logo field, then save the changes. Note than you can use files stored in the File Library (go to File Libary Overview for more information).

Important
Depending on the country in which your Reportal users are located, providing information about the use of cookies may be necessary for your company to comply with local regulations. For more information, refer to the Forsta website at https://legal.Forsta.com/legal/privacy-notice/.

Important
Saving automatically publishes the changes to the users' login page.

Fiscal Calendar

The Fiscal Calendar tab - allows you to set up non-standard fiscal calendars such that you can later create reports based on your company's accounting time-plan.

Users with the Company Administrator permission can set up calendars through the Admin menu or via the Home > Company > Company Settings menu.

Figure 4 - The Company Settings > Fiscal Calendar tab with no existing calendars

Note: The Fiscal Calendar functionality will be available only for reports using the Extended Tabulation Engine. Refer to the Reportal documentation for further details on the Extended Tabulation Engine.

You can enter the calendar dates manually, or copy and paste from a tab-delimited .txt file created in another application such as Notepad.

Creating a Fiscal Calendar Manually

To create a calendar and enter the dates manually:

1. In the Fiscal Calendars tab, click Add.

A calendar is created and added to the list - .



Figure 5 - A new calendar is added to the list

2. Click into the calendar name field and change the name to something suitable.
3. Click Edit to open the calendar editing overlay - .



Figure 6 - The empty editing overlay

4. Click Add.

A default calendar is displayed - .



Figure 7 - The default fiscal calendar that is created when you click Add

5. Fill in the year, select the month and fill in the day for each row as required.
6. On completion click Save to save the calendar.

To delete a row or rows from the table, check the relevant box(es) to the left of the row(s) and click Remove.

This calendar can now be used in your Reportal reports. Refer to the Reportal documentation for further information.

Copying and Pasting a Fiscal Calendar

Note: The data must be available as a tab-delimited txt file, with the columns in the order Year Month Day - .

To copy the data into the fiscal calendar from a .txt file:

Figure 8 - Example of a .txt file from which the calendar dates can be copied

1. In the tab-delimited .txt file, select and copy the required information, then return to the Fiscal Calendar tab, click into the field on the right, right-click and select Paste.

Note: In a FireFox browser, you must first click Add to create a row in the table, then click into the row and click Paste to copy the data in.

The data is copied into the field - .



Figure 9 - Copied Data

2. Edit the data if required, then when it is correct click the << button.

The data is copied into the appropriate columns of the calendar - .



Figure 10 - The data copied into the calendar

3. In the Fiscal Year column set the start year and select the start month.

For the example these are 2015 and January. The Fiscal Year and Fiscal Month columns are then populated.

4. Click Save to save the changes.

To delete a row or rows from the table, check the relevant box(es) to the left of the row(s) and click Remove.

This calendar can now be used in your Reportal reports. Refer to the Reportal documentation for further information.

Other

To access the options on the Other tab, go to the Home > Company > Company Settings menu command and select Other. The tab opens as shown below - .

Figure 11 - The Company Settings > Other tab

Note: Users with the Company Administrator permission will have access to the properties above.

The options are as follows:

• Set "Do not perform data cleaning on Conditions" as default - In Forsta Designer, if a condition evaluates to FALSE, the answers to all questions inside the THEN folder are deleted. (If it evaluates to TRUE and has an ELSE folder all the answers to the questions inside the ELSE folder are deleted.) This is to ensure consistency in the data if the respondent moves back and forth in the Survey and changes his/her answers (if you have allowed the respondents to modify their answers). However sometimes you do not want to delete the previously entered data. This could for example be in a Survey where the respondent is allowed to re-enter, but should only get access to some of the questions or a different set of questions than the first time. In a Condition’s Details page, the author can check the “Do not perform data cleaning” property to prevent deletion of the answers inside a THEN or ELSE folder with a check that this is the first or second time the user accesses the survey. However, as the administrator you can check this box to set the property as default for the entire company.
• Set "No cleaning on question masking" as default - Under normal circumstances, if a Question Mask evaluates to FALSE, the question is hidden and the answers to the question are deleted. This is to ensure consistency in the data if the respondent moves back and forth in the Survey and changes his/her answers (if you have allowed the respondents to modify their answers). However sometimes you do not want to delete the previously entered data. The question property "No cleaning on Question Masking" will prevent this cleaning. A system or company administrator can select the company setting "Set 'No cleaning on Question Masking' as default" for the entire company.
• Do not show survey name in browser title - When this setting is enabled, the browser title will contain the URL for the survey and the survey name will not be displayed, irrespective of what is defined in the survey or mobile layout, for all rendering modes. This setting is only applied after launching a survey and cannot be overridden with a survey setting.
• Ascribe account ID (FTP) - Use this field to view the Ascribe ID used for transferring Ascribe exports. Ascribe(TM) is an application for coding open text (verbatim) responses, provided by Language Logic (http://www.languagelogic.info) and is not part of the Authoring offering or part of any product of service provided by Forsta Company. The Ascribe export will give an XML file with Survey and codebook definitions, as well as response data. It gives you a simple way to transfer the data from Authoring to Ascribe. To use the FTP option, your company's Authoring account must be set up with the correct FTP settings for the Ascribe FTP site. You must establish an Ascribe account by contacting Language Logics directly, and you will receive the relevant FTP account name from them.
• Enforce optimized data storage - Enabling this option will enforce that all survey databases created will be in the optimized database format, the legacy database format will not be available as an option. This setting applies to all new surveys created, either via the New Survey menu item, duplication of an existing survey or by importing of a survey XML. Any existing surveys created in the legacy format will remain in this format even if re-launched.
• Email Sender for Data Exports - if you wish to set up a standard Sender email address for your company, type the address here. This address will then be used throughout the company as the Sender address for data exports sent via email, FTP notifications and ‘Failed import / export’ emails to the user.
• Recipients of Archiving notification emails - notification messages regarding the archiving of projects for your company will be sent to the email addresses specified in this field in addition to the project creator (go to About Archiving for more information). This allows management of archiving processes even if the person who actually created the project is unavailable or has left the company. You can specify one or several e-mail addresses on the company level, separated by semi-colon (;).
• Google Analytics Account ID - Use of this feature causes data to be sent to a third party processor (Google) outside Forsta's control. Forsta explicitly disclaims any warranty of this feature, and support may be provided at Forsta's discretion only (go to Google Analytics Integration for more information).