Notifications
Types
| Type | Fires when |
|---|---|
| Issue status change | An issue you reported changes status |
| Issue comment | Someone comments on your issue |
| Issue assigned | An issue is assigned to you or your group |
| Announcement | A new announcement is posted |
| Announcement comment | Someone comments on an announcement you follow |
| Message | A new message in one of your conversations |
| Payment reminder | Something is due |
| Upcoming autopay | A subscription is about to charge itself. Nothing is owed and no action is needed |
| Fee published | A new fee applies to you |
| Violation notice | A violation is filed against your property, or escalated |
| Board post | A new post on the community board |
| Board comment | A comment on a board post |
| Board flag | Content was flagged. Admins only |
| Booking cancelled | An admin cancelled a reservation of yours |
Channels
Three, and they are not configured separately:
- In-app, the bell in the header. A feed with read state.
- Email, branded with the community's logo and colours where branding is on.
- Push, on the mobile apps.
Read state syncs across the web and mobile, so reading something on a phone marks it read everywhere.
Who controls what
Each member controls their own preferences per category, in notification preferences. Everything is on until they turn it off.
Admins do not configure a member's preferences and cannot override them. A notice that must reach everybody should be an announcement, a broadcast, or both, rather than a notification setting.
Why upcoming autopay exists
A subscription charge that appears on a statement unexplained generates a support ticket. A notice a few days ahead does not. The notification is deliberately worded as nothing needing action.