Platform › Connectivity
What this company sends by email, to whom, and what became of it. Every message goes from noreply@tranxact.ai unless you send from your own domain. An account being created, a requisition raised, a purchase order waiting for its approver, a ticket answered — each event has a default audience, and a rule of your own replaces it.
In Platform → Connectivity · 6 screens
RecordsEmail SettingsThe sender and the way mail leaves. "Platform" sends through this deployment’s own Microsoft 365 account as noreply@tranxact.ai. Choose Microsoft 365, SMTP or a mail provider to send through your own account and domain instead — the credential is sealed on the way in and never shown again. A company has one set of email settings: open it, press Edit, then Set credential and Send a test.OpenRecordsEmail RulesYour own decision about an event: who receives it and in what words. Any rule for an event replaces its default, so an inactive rule is how an event is switched off. Any screen’s <module>.<screen>.created, .updated or .status_changed can have a rule.OpenViewEmail EventsEverything the product sends by email, and who receives it when you have written no rule.OpenRecordsSupport CopyEvery step of every support ticket — raised, answered, assigned, escalated, resolved, closed — sent by email to the support desk within a minute of it happening. support@tranxact.ai unless you change it. Only what happens from the moment copying began is sent, and internal notes stay inside unless you tick them in.OpenViewEmail OutboxEvery message: to whom, about what, and what the mail server said. A failed one is retried on its own; a held one goes as soon as a transport is configured, unless it is three days old by then.OpenWorkspaceEmail SuppressionsEverybody who pressed Unsubscribe in an email, or was unsubscribed for them. An address here is sent nothing by any company in this system, except a message the person asks for themself to get into their own account. Re-subscribing one needs a reason, and is audited.Open
Columns, fields and actions
| Screen | Kind | What it is | Columns | Fields | Actions |
|---|---|---|---|---|---|
| Email Settings | List | The sender and the way mail leaves. "Platform" sends through this deployment’s own Microsoft 365 account as noreply@tranxact.ai. Choose Microsoft 365, SMTP or a mail provider to send through your own account and domain instead — the credential is sealed on the way in and never shown again. A company has one set of email settings: open it, press Edit, then Set credential and Send a test. | 7 | 11 | 2 |
| Email Rules | List | Your own decision about an event: who receives it and in what words. Any rule for an event replaces its default, so an inactive rule is how an event is switched off. Any screen’s <module>.<screen>.created, .updated or .status_changed can have a rule. | 5 | 6 | 0 |
| Email Events | Read-only list | Everything the product sends by email, and who receives it when you have written no rule. | 5 | 0 | 0 |
| Support Copy | List | Every step of every support ticket — raised, answered, assigned, escalated, resolved, closed — sent by email to the support desk within a minute of it happening. support@tranxact.ai unless you change it. Only what happens from the moment copying began is sent, and internal notes stay inside unless you tick them in. | 6 | 3 | 1 |
| Email Outbox | Read-only list | Every message: to whom, about what, and what the mail server said. A failed one is retried on its own; a held one goes as soon as a transport is configured, unless it is three days old by then. | 9 | 0 | 1 |
| Email Suppressions | Workspace | Everybody who pressed Unsubscribe in an email, or was unsubscribed for them. An address here is sent nothing by any company in this system, except a message the person asks for themself to get into their own account. Re-subscribing one needs a reason, and is audited. | 0 | 0 | 0 |