Alerts
Where a creator's alerts go, as far as a connector may ask or change it — the one switch for the account in front of the connector, and what the core keeps to itself.
Subscriby\Connector\Core\Alerts. The core keeps a creator's alert destinations: which accounts, addresses and (later) devices carry which classes of alert (a sale, a waiting member, an incident, a security event). A connector's admin surface offers the creator exactly one switch for the account it is talking to: whether the core's alerts reach them through that account. The set_alert_destination command in the catalogue is this contract.
Methods
| Method | Returns | Meaning |
|---|---|---|
receivesAlerts(CreatorRef $creator, IdentityRef $identity) | bool | Whether any class of alert reaches the creator through that account. |
setReceivesAlerts(CreatorRef $creator, IdentityRef $identity, bool $receives) | bool | Route every class through the account (true) or none (false). Returns false when the core knows no such creator or the account is not theirs. |
if ($alerts->receivesAlerts($creator, $identity)) {
$alerts->setReceivesAlerts($creator, $identity, false); // "Stop sending my alerts here"
}What the core keeps to itself
- The classes. Which alert classes exist, which are critical, and the finer routing a creator sets on the dashboard's Notifications settings (this class here, that class there). A connector sees all or nothing for its account.
- E-mail for the critical classes. Whatever the switch says, the core still mails the critical classes (billing, security, recovery) to the creator's verified address. A connector cannot switch e-mail off.
- Other connectors' accounts. The contract takes the identity in front of you; it never lists or changes destinations on another connector.
What the ref carries
CreatorRef: id and locale, so the confirmation you send back is in the creator's language.
The switch is per account, not per installation
A creator with two project bots on your connector still has one account on the platform; alerts are routed to the account, and both bots may render the same switch. Read before you write, and say what you did.
How is this guide?
Creators
Creator accounts as a connector may create them — the one call that turns a connector's sign-up form into an email-first account with a linked identity, and the two ways it is refused.
Recovery
What the application keeps ready for a project's recovery, as a connector may read it — the coverage object behind the readiness checklist — and the two places a connector files, a standby and a replacement, through the actions the dashboard runs.