For arlanix/notification 1.0.0

Before you start

Notifications are sent from the store's background jobs, by email, Telegram, Slack or Discord. Your developer sets them up once; after that everything is done in the admin.

Ask your developer for

• The modules you need. The installation guide is written for them. Email, Telegram, Slack, Discord, the store's events (orders, customers, reviews) and monitoring (cron, errors, orders that stop, admin sign-ins, imports and exports) are each a module of their own: all of them come together, or only those you name. Arlanix Product Feed, when the store has it, brings events of its own: a feed that fails, delivers again or leaves products out.
• Email that works. By default notifications go the way the store's order emails do: if those arrive, notifications will. To send them through a mail server of their own instead, such as your company's or a service like Amazon SES or Postmark, see Email.
• The background jobs running. Notifications are sent by a Magento background process, the queue consumer, which the store's cron starts. Most stores already run it.
• For Telegram, a bot. Anyone can make one in a minute: see Telegram. Slack and Discord need nothing set up beforehand.

Check it was done

1. Open Arlanix > Notifications > Topics. The page opens; the developer's check may have made a topic there, or you make one now (Topics).
2. In your first rule, the test message arrives within a minute. If it does not, see Troubleshooting.

Who can see it

An admin user sees the Notifications pages their role allows, in System > Permissions > User Roles: see Admin roles.