Workspaces Notifications

(Requires Workspaces module) When a Web Transfer Client user shares a folder, an invitation is sent to the user with whom the folder is shared. If the recipient does not have an account on EFT, the user can register the account. For invitations sent to non-EFT users, an email is sent to verify the account when the user registers the account.

The text for the invitation and verification emails is contained in an HTML file that can be customized for localization or to provide company-specific information.

Workspaces invitations expire after 5 days.

The templates are stored in \ProgramData\Globalscape\EFT Server or your cluster share under Templates, and apply to all Sites on the Server.

You can edit the files in any text editor. Note that the "WS" variables used in these notification templates are used only in these templates. They are not Event Rules variables. (Refer to Workspaces Events and Workspaces-Related Variables for additional means of notification.)

NOTE: The Event Rules context variables are intended for use in the Event Rules subsystem. The Workspaces variables are not Event Rule variables and are outside of that subsystem. They are only used for Workspace notifications.

The files are named per their function:

  • WorkspaceNotification.txt - Used to notify the Workspace owner that a recipient took an action on a file.

  • WorkspacesadministratorAddedParticipantMsg.html - Used to notify recipients that a Workspace was shared with them.

  • WorkspacesInviteRegisterMsg.html - Used to notify recipients that a Workspace was shared with them and they are invited to register an account on EFT.

  • WorkspacesInviteVerifyMsg.html - Sent after recipient has registered for an EFT account and needs to verify the account.

  • WorkspacesOAIEmail.html - Notification to recipients that a file has been sent from Outlook.

    • WorkspacesOAIEmail.txt - Text version of the notification to recipients that a file has been sent from Outlook.

  • WorkspacesOAIEmailWithSecureMB.html - Notification to recipients that a file has been sent from Outlook with secure message body.

    • WorkspacesOAIEmailWithSecureMB.txt - Text version of the notification to recipients that a file has been sent from Outlook with secure message body.

  • WorkspacesRequestFileEmail.html - Notification to sender that a file has been requested.

    • WorkspacesRequestFileEmail.txt - Text version of the notification to sender that a file has been requested.

The following variables can be used in Workspaces notification templates:

To edit the Workspaces invite and verify messages

  1. In the administration interface, connect to EFT and click the Server tab.

  2. On the Server tab, click the Server node.

  3. In the right pane, click the General tab.

  4. In the General Settings area, next to Workspaces invite message, click the browse icon. Your default text editor (for example, Notepad) opens with the invitation text in HTML.

  5. Edit the text as needed, being careful not to delete the variables (%USER.EMAIL_ADDRESS%, %WS_OWNER_NAME%, %FOLDER_NAME%, %LINK%), then save the file and close the text editor.

    The WS_ variables are not Event Rule variables. To use Workspaces variables in Event Rules, refer to the Variables list.

  6. Next to Workspaces verify message, click the browse icon. Your default text editor (for example, Notepad) opens with the verify text in HTML.

  7. Edit the text as needed, being careful not to delete the variables (%USER.EMAIL_ADDRESS%, %LINK%).

  8. In the General Settings area, next to Authentication OTP message, click the browse icon. Your default text editor (for example, Notepad) opens with the message text in HTML.

  9. Edit the text as needed, being careful not to delete the variables, such as {{USER.EMAIL}}, then save the file and close the text editor.

  10. Save the file and close the text editor.

To create Site-specific versions

(See also Specifying External and Internal Domains)

  1. Make a copy of the existing template.

  2. Make your edits (using a text editor, such as Notepad), being careful not edit any of the variables or necessary code.

  3. Save the edited version with the Site name and an underscore prepended to the front if the filename. For example, name it MyFrenchSite_PasswordResetMsg.html