FTAPI Version 4.68.0

New

FTAPI Trust Network

• Directly connected to every FTAPI partner: Your organization is automatically connected to all other FTAPI organizations. As soon as your e-mail domain is validated, deliveries from other organizations arrive directly in your employees' FTAPI Inbox, without a guest account on someone else's system and regardless of whether your partners follow suit. Once your partner has validated as well, this applies in both directions. Your network grows on its own with every new FTAPI customer, and the coordination between IT departments and the exchange of API keys per partner are no longer needed. Deliveries remain end-to-end encrypted and are scanned for viruses as usual; download confirmation and the activity log work as before. With this version, automatic networking applies to all customers. For the overview, see FTAPI Trust Networks: overview and automatic networking; the course of a delivery is described in FTAPI Trust Networks: function and process.
  • Validate your domain, and that is it: Under "Configuration → My Domains", administrators add the e-mail domain and set the TXT record in the DNS. Verification is certificate-based, with no key exchange, and the benefits apply immediately after validation. Step-by-step guide.
  • Check the group and its license: Under "Trust Network → Settings", administrators define the user group for new users. Assign a SecuMails license to that group so your employees can also reply to incoming deliveries.
  • See who you are connected with: The admin panel lists all active connections of your instance, with the partner organization's name or domain and the first and most recent exchange. For audits and data protection enquiries, the current state is available at any time. Learn more.
  • Preparing your users: Recipients who receive a delivery from another organization for the first time will find the explanation in an article you can pass on: I have received a delivery from another organization.
  • Manual connections: Setting up individual connections by hand is no longer needed; connections are established solely through the central registry. The former setup via API keys is still documented here.

SecuRooms

• Configurable trash bin retention period: Administrators now define how long deleted files, folders and data rooms remain in the trash bin before they are removed permanently. The default is 30 days, the maximum is 90 days. Until the period expires, items can be restored from the trash bin; afterwards the system deletes them permanently and automatically. The trash bin page shows the configured period instead of a fixed value. The setting is located under "Administration → SecuRooms → Settings → Manage trash bin".
• Manage group access without administration rights: Data room owners now invite user groups into the data rooms they own, and remove them again, themselves. Departments organize their collaboration on their own, and IT no longer receives a request for every single group assignment. Administrators grant the new permission "May invite user groups into data rooms" per user group in the administration, alongside the other SecuRooms permissions. It applies only to data rooms the user owns and requires the permissions "Web UI access", "Access to SecuRooms" and "Can share existing data rooms with others", which are enabled automatically along with it. The permission is licensed: a user holding this SecuRooms permission and no other counts as one SecuRooms licence.
• Resizable folder tree sidebar: The folder tree sidebar can be dragged to the width you need using its right-hand edge. In deeply nested structures with long folder names, the names stay readable and your position in the tree stays visible. The width you set is kept after a page reload, but not beyond the session. The full folder path is still available as a tooltip when you point at an entry.
• Sort the data room overview by number of members: In the administration, clicking the "Members" column header sorts the data room overview by member count; clicking again reverses the direction. This makes data rooms with the broadest access easy to find without paging through the list. The sort applies to the entire list and can be combined with the name search.

SecuMails

• Encryption method distribution in the "Intelligent Email Encryption" dashboard: A bar chart now shows which encryption methods were used for the e-mails sent successfully via the gateway. This makes it visible which methods your recipients actually support.
• E-mail log export in the "Intelligent Email Encryption" dashboard: An export button in the e-mail log downloads the log entries as a CSV file, up to 500,000 entries per export. Evaluations and records can therefore be processed further outside FTAPI.

Improved

SecuRooms

• Uploads continue after an interruption: If the connection drops during an upload, or the server is updated at that moment, the upload picks up where it left off instead of starting over. This now also covers uploads into end-to-end encrypted data rooms, which have been moved to the same path. Large files and uploads over unstable connections therefore reach the data room reliably.
• Data room wide access management with duplicate roles: Duplicate role entries blocked actions that change access for an entire data room. These actions now complete, and affected data rooms can be managed data room wide again.

SecuMails

• Clearer deletion in the Outbox: When a sender deletes a delivery from the Outbox, FTAPI now states the consequences beforehand. The delivery disappears from the sender's own Outbox, and the file attachments are removed at the recipient. The delivery stays visible in the recipient's Inbox, so they can see why it can no longer be retrieved instead of asking the sender.
  • For security levels 1 to 3, the subject and message stay visible to the recipient, and attachment names are no longer shown.
  • For security level 4, the message text is removed as well.
  • This behaviour is now identical across all delivery channels, including deliveries via FTAPI Trust Networks.
• Download confirmation for security level 3 and 4 deliveries: For end-to-end encrypted deliveries with several attachments, the completion of the download was not always recognized when a file was retrieved more than once. The delivery then stayed marked as not retrieved, with no confirmation e-mail and no corresponding event. This mainly affected downloads in mobile browsers, which request files repeatedly on their own, and access via the REST interface. The tracking has been reworked: the download is now recognized reliably, no matter how often a file is retrieved along the way.
• Attachments in level 3 deliveries without a SecuPass: Recipients of a security level 3 delivery who had not set up a SecuPass could see the delivery but received a permission error when accessing its attachments. Those users can now set up a SecuPass as usual and, once the sender has granted access, download the attachments.
• Sender in the download report for delivery downloads: For uploads via a SubmitBox, the download report showed the recipient as the sender. It now shows the person who actually uploaded the files, so uploads can be attributed clearly.
• Call to action in the level 4 delivery notification: The body text of the e-mail asked recipients to "release" the delivery, while the button is labelled "Complete". Text and button now match, so recipients can identify the next step. [placeholder: English labels of the body text and the button.]
• Intelligent Email Encryption without a sender language: If no language was set for a sender, the e-mail pre-check aborted. When no language is set, the default notification language now applies and the e-mail is processed normally.
• Secure send from Outlook without a configured expiration: If no delivery expiration was configured on the server, the Outlook add-in rejected secure send. Sending now works in this configuration as well.

SecuForms

• Translation of the "Template" field type after a language change: After switching the language, this field's label appeared in the new language only after a page reload. The label now changes immediately with the language selection.

Platform

• Faster two-factor login: The code field is now selected as soon as the second login step opens. You can type or paste your code straight away, without clicking into the field first. This applies to all three methods: authenticator app, SMS and e-mail verification code. If a code is rejected, the cursor returns to the field with the old code highlighted, so simply retyping replaces it. A login that fails because of a lost connection is now reported as a connection error instead of an incorrect code.
• Error message on a failed login: When several authentication providers are configured, the login page gave no feedback after a failed attempt. Network errors are now shown on the login page, so users can see the reason instead of contacting support.
• Modernized interface in administration, reports and account settings: The older page areas now use the same colours, radii, buttons and typography as the rest of the interface, so the web interface looks consistent throughout. Yes/no settings in configuration forms appear as checkboxes whose state is visible at a glance. These pages also support pinch-to-zoom now. The changes are purely visual; click paths and functions remain unchanged.
• Storage display split by SecuMails and SecuRooms: Used storage is now broken down by SecuMails and SecuRooms, in the administration, in the user view and in the edit-user dialog. Administrators can therefore see which product is using an account's storage and clean up or adjust quotas accordingly.
• Stricter rules for content loaded in the browser: Via the Content Security Policy, the web interface now states explicitly which sources scripts, images, fonts and connections may be loaded from, and no longer permits embedded scripts. HTTP calls are upgraded to HTTPS automatically. Injected script code can therefore no longer be executed in the browser.
• Video embeds on the login page: A YouTube video embedded as a hint on the login page showed video player error 153. Embedded videos now play again.

FTAPI cloud customers do not need to take any action, the update will be performed automatically. Customers can receive detailed information about the maintenance window via status.ftapi.com.

Information on On-Premises

Customers with an on-premises operating mode, please follow the instructions in the update guide. Click here for the download area.