Mox Email Notifications
Here is a summary of Mox emails and notification settings.
Mox User Account and Access Emails
Mox will always send emails for subscriptions and actions related to user access, such as activate account, invite user, welcome to workspace, and forgot password.
Email Subject Sample | Trigger | Sent To | |
User Registered | Thanks for signing up for Mox! | A brand new user (no existing Esko ID) signs up for a Mox trial | The trial registrant |
Account Activation | Welcome to Mox! | Brand new user (no Esko ID) is invited to an account/workspace | The invited user |
Workspace Welcome | Mox Invitation: <Workspace Name> | Existing user (with Esko ID) is invited to an account (and workspace) that they are not yet part of, OR | The invited user |
Forgot Password | Thanks for signing up for Mox! | User clicks Forgot Password link on Mox sign in page | The user initiating the Forgot Password action |
Invited To Project | Mox Invitation: <Project Name> | A user is invited to a project or sub-project | The invited user |
Workspace Notification Emails
The following emails are optional. A workspace owner or account owner can turn these emails on or off for a workspace in Settings > Notifications.
Note: Mox will not send emails to the user who performed the action.
For example, If you are the Project Owner and if you assign yourself to the first task and you are the one that puts the project in progress, it will not send an email. If you do back to back (in other words, the 1st task and then, the 2nd task is assigned to you), you will get the notification for the 2nd task going in progress.
Task Ready
(Default = ON) | Task/Project/Sub-Project Ready! <Project Name>: <Task Name> | A task, project or sub-project is assigned and ready to work on. | The task, project or sub-project owner |
Task Unassigned
(Default = ON) | Project/Sub-Project/Task Unassigned! <project name>: <task name> | A task, project or sub-project is no longer assigned; no further action is required at this time. | The task, sub-project or project owner |
Task Completed
(Default = OFF) | <Project Name>: <Task Name> - Completed | A task is completed. | The project managers (and sub-project managers if the task is in a sub-project) |
Asset Approved
(Default = OFF) | <Project Name>: <File Name> - Approved | An asset is approved by a user.
| The project managers (and sub-project managers if the asset is in a sub-project)
|
Asset Changes Requested
(Default = ON) | <Project Name>: <File Name> - Changes Requested With Comment.
OR
Project Paused: <Project Name>: <File Name> - Changes Requested With Comment | An asset has changes requested by a user. | The project managers (and sub-project managers if the asset is in a sub-project) |
Asset Locked
(Default = OFF) | Final Decision! <File Name> in <Project Name>)
OR
Project Paused: Final Decision! <File Name> in <Project Name>) | A locking decision (Approved or Changes Requested) is set on an asset.
| The project managers (and sub-project managers if the asset is in a sub-project)
|