Catalog
In Admin > Notification Settings > Email, you can configure email notifications.
1. Configure a sender email account
Go to Admin > Notification Settings > Email. You must configure a sender mailbox first, then click Next.
图1
Common SMTP providers (examples)
- Gmail / Google Workspace:
smtp.gmail.com— Port 587 (STARTTLS) or 465 (SSL). Authentication typically uses the full email address as the username. Many accounts require an App Password (instead of the normal login password) when using SMTP clients. - Microsoft 365 / Outlook (Exchange Online):
smtp.office365.com— Port 587 (STARTTLS). SMTP authentication may need to be enabled for the mailbox/tenant. If your tenant restricts legacy SMTP authentication, use an approved mail relay/connector as per your organization’s policy. - Company SMTP relay (recommended for enterprises): Use your organization’s internal SMTP relay hostname/IP, port, and authentication method (or connector-based relay), as provided by your IT/email administrator.
- You can use any SMTP service (corporate SMTP/Exchange, cloud email services, etc.) as long as you have the SMTP server address, authentication method, and any required app password/security token.
2. Configure sender mailbox settings
Fill in the basic SMTP configuration for the sender mailbox.
图2
Click Save. After saving successfully, you can test whether sending works properly.
图3
3. Send a test email
From the dropdown list, select a user in Sanplex.
图4
Click Send Test Email. If the configuration is correct, the selected user will receive a test message.
图5
4. Configure email notification triggers
In Notification > Settings, you can configure which actions trigger Sanplex to send email notifications.
图6
By default, Sanplex includes triggers such as:
- Bugs: When actions such as Create, Edit, Assign, Confirm Bug, Resolve, Activate, Close, or Import into a Project occur, emails are sent to Assignee and CC recipients.
- Requirements: When actions such as Create, Edit, Change, Activate, Review, Close, or Update Plan/Branch/Stage/Assignment occur, emails are sent to Assignee and CC recipients.
- Tasks: When actions such as Create, Edit, Assign, Start, Finish, Activate, Close, Cancel, or Restart occur, emails are sent to Assignee and CC recipients.
- Test Requests: When Create or Edit occurs, emails are sent to the Owner and CC recipients.
- After a Requirement is linked to a Project, if the Requirement changes, an email reminder is sent to all Project members.
- When a Build is submitted for testing, an email reminder is sent to the Test Owner.
