Create a profile
Open System → Email & templates → SMTP with email.manage. Enter profile name, public SMTP hostname, username, password, From email, From name and optional Reply-to. Use port 465 with implicit TLS (smtps) or 587 with required STARTTLS (starttls). The application requires peer-verified TLS; changing the port to bypass certificate errors is not a repair.
SMTP is the transport contract. A provider's SMTP credentials may work when it supports these exact requirements; this does not imply a separate Gmail, Microsoft, SES, Mailgun, SMS or transactional-API connector is bundled. Follow the mail provider's current authentication and sending-domain requirements separately.
Verify actual delivery
Saving clears the profile's previous verification. Send Test to the signed-in administrator's mailbox. Enter the 8-digit code within 10 minutes; five failed guesses require a fresh test. Tests are bounded to three per staff member per minute. Provider acceptance alone is not sufficient: receive the message and enter its actual code.
Map routes
In Routes, choose verified primary and distinct fallback profiles for security, billing, support and general. A support department may have its own verified profile. Configure each brand/storefront's explicit map as needed. An empty brand map does not borrow a different seller's sender. Security mail enables verification/reset/invitation journeys; billing mail carries invoice notifications and their matching PDF.
Verify the finished workflow
Use a disposable staging account to request verification/password setup and issue a test invoice through the normal staging workflow. Inspect the stored recipient, brand, portal link and sender as well as actual inbox receipt. Profile changes do not rewrite queued sender snapshots. Save new settings, verify again, then use outbox recovery for held historical messages.