Compare email encryption, local or object storage, backup transports and connection-test results.
Choose the email provider’s supported encryption#
Use the host, port, encryption mode and credentials supplied by the selected email provider. The settings must match; choosing a familiar port does not test that the server can send mail.
| Choice | When it fits | What it changes |
|---|---|---|
| STARTTLS · commonly port 587 | The provider offers an SMTP submission connection upgraded to TLS. | Select STARTTLS and the provider’s matching port. Confirm the connection and actual delivery through the supported test. |
| SSL/TLS · commonly port 465 | The provider expects TLS from the start of the connection. | Select SSL/TLS and the matching port. It is a different connection mode, not an extra layer to add on top of STARTTLS. |
Local storage or S3-compatible storage?#
Changing a connection does not automatically migrate existing files. Preserve the old data and follow a reviewed migration and recovery plan before retiring a storage location.
| Choice | When it fits | What it changes |
|---|---|---|
| Local storage | Files remain on the configured application storage. | Uses the existing storage and backup arrangements. A server move must include the protected files. |
| S3-compatible object storage | Use a supported external object-storage service. | Requires the correct endpoint, bucket, region and protected credentials. Keep objects private and verify the actual connection. |
Choose a supported backup transport#
Backup transport describes how an encrypted backup repository reaches its configured destination. A successful upload does not establish that recovery has been tested.
| Choice | When it fits | What it changes |
|---|---|---|
| FTPS | A supported FTP service protected by TLS. | Uses the provider’s FTPS host and login. It is different from unencrypted FTP and from SFTP. |
| SFTP | A supported file-transfer destination over SSH. | Requires a verified host and the configured SSH/SFTP access. Host identity checks must remain enabled. |
| S3-compatible destination | Store encrypted repository objects in a supported object-storage service. | Requires the correct HTTPS endpoint and bucket access. Verify replication and an independent restore. |
Saved settings are not tested readiness#
A saved connection can still have the wrong permissions or endpoint. Use the supported connection test and review its result. For email, also verify actual inbox delivery; for backups, verify a restore.
Keep production and disposable-demo credentials separate. Never paste provider secrets into ordinary notes or a support conversation.
Review the platform seller before enabling paid sales#
These system settings identify Emnaro as the seller of platform subscriptions, development services and optional licences. They are separate from a customer business’s own invoicing identity and merchant accounts.
Save the actual registered seller name, business address, applicable registration number and billing contact. Review the published terms and payment configuration before changing commercial readiness.
| Choice | When it fits | What it changes |
|---|---|---|
| Not ready for paid sales | Keep paid sales unavailable while the commercial setup is incomplete. | Saving seller details does not by itself enable paid checkout. |
| Seller details and terms reviewed | Record the administrator’s commercial activation decision. | Paid checkout still requires the supported production Airwallex configuration and verified payment lifecycle. This choice does not approve a merchant account or prove regulatory compliance. |
Enable free-workspace advertising with the required consent#
System advertising settings apply only to eligible free workspaces. Paid workspaces remain ad-free. Configure the publisher and ad-unit identifiers before enabling the connection; entering an identifier does not establish publisher approval.
Ad delivery also depends on the applicable user consent. Keep the consent-platform readiness choice unverified until the required Google-certified consent management platform has been configured and tested. The readiness setting does not install a consent platform.
| Choice | When it fits | What it changes |
|---|---|---|
| Advertising disabled | Keep platform advertising off. | A saved publisher identifier alone does not enable ad delivery. |
| Advertising enabled | Permit advertising in eligible free workspaces. | The platform still checks package eligibility, configuration and applicable user consent. This does not insert ads into paid workspaces. |
| Consent platform not verified | Keep the restricted-region consent gate closed. | Do not change this simply to make ads appear. Complete the actual provider configuration first. |
| Certified CMP configured and verified | Record the completed consent-platform setup. | For personalised advertising in the EEA, UK and Switzerland, the required Google-certified TCF consent platform must actually be configured and verified in the publisher account; user consent remains necessary. |
Keep the active workspace, actual business requirements and current setup summary in view. A guide explains a choice; it does not make that choice for you.