News Items
Property managers publish common or emergency announcements to residents of specific buildings or units.
Notification Channels
Push, SMS, email, and Telegram — messages are dispatched across all channels the resident has enabled.
Templates
Reusable templates speed up publishing routine news such as scheduled outages.
Resident Preferences
Residents and organizations can opt out of specific notification types.
News Items
ANewsItem is an announcement created by an organization and delivered to residents via push notification. Key fields:
| Field | Description |
|---|---|
title | Headline of the announcement |
body | Full text of the announcement |
type | common or emergency |
sendAt | Scheduled send time (must be in the future) |
validBefore | Expiry date — residents cannot see the item after this date |
organization | Publishing organization |
News Types
| Type | Constant | Push Notification Type |
|---|---|---|
| Common | NEWS_TYPE_COMMON | NEWS_ITEM_COMMON_MESSAGE_TYPE |
| Emergency | NEWS_TYPE_EMERGENCY | NEWS_ITEM_EMERGENCY_MESSAGE_TYPE |
News Categories
News items can be tagged with a category to help residents filter their notification feed. Available categories:WATER, HEATING, ELECTRICITY, GAS, ELEVATORS, ELECTRICITY_AND_ELEVATORS, UTILITIES, TELEPHONE, METERS, CLEANING, INTERCOM, SNOW, FIRE_PROTECTION, OTHER
Targeting with Scopes
Every published news item must have at least oneNewsItemScope. Scopes define who receives the announcement.
| Scope Type | Targets |
|---|---|
organization | All residents across all properties in the organization |
property | All residents of a specific building |
property_unitType | All residents of a given unit type within a building |
property_unitType_unitName | A single specific unit in a building |
type field on the scope is calculated automatically from the combination of property, unitType, and unitName values provided.
Publishing a news item without any scopes raises a
NO_NEWS_ITEM_SCOPES error. At least one scope is required.Recipient Count Preview
Before publishing, managers can callGetNewsItemsRecipientsCountersService to preview how many residents will receive the announcement, broken down by scope.
News Templates
NewsItemTemplate records provide reusable starting points for common announcements. Each template has:
name— Template display name (e.g., “Heating outage due to repairs”)type—commonoremergencycategory— Suggested category (e.g.,HEATING)title— Pre-filled headlinebody— Pre-filled body textorganization—nullfor system-wide templates, or scoped to an organization
Publishing a News Item
Draft the announcement
Fill in
title, body, type, and optionally category. The system checks for profanity in both fields and rejects content that fails validation.Set scopes
Add one or more
NewsItemScope records to define the target audience (organization, property, or specific units).Schedule or send immediately
Set
sendAt to a future date/time, or leave it to send within the default delay window (SENDING_DELAY_SEC). Validity can be capped with validBefore.News Sharing
For multi-organization deployments,NewsItemSharing allows a news item from one organization to be shared to others. GetNewsSharingRecipientsCountersService and GetNewsSharingRecipientsService help identify the audience before sharing.
System Notifications
Beyond news, Condo sends dozens of automatedMessage records for system events. All messages go through the same transport pipeline.
Notification Transports
| Transport | Constant | Notes |
|---|---|---|
| Push | PUSH_TRANSPORT | Firebase (Android), APNs (iOS), RedStore |
| SMS | SMS_TRANSPORT | Via configured SMS adapters |
EMAIL_TRANSPORT | HTML templated emails | |
| Telegram | TELEGRAM_TRANSPORT | Via TelegramUserChat bot integration |
Message Statuses
| Status | Meaning |
|---|---|
sending | Queued for delivery |
processing | Being processed by transport |
sent | Accepted by transport provider |
delivered | Confirmed delivered to device |
read | Opened by recipient |
error | Delivery failed |
blacklisted | Recipient opted out |
canceled | Suppressed before sending |
throttled | Rate-limited |
disabledByUser | Disabled via user preferences |
Push Notification Types
Push notifications support two modes:default— Visible notification with title and bodysilent_data— Background data payload without visible alert
android, ios, web.
Resident Notification Preferences
Residents can manage their notification subscriptions through:NotificationUserSetting— Per-message-type opt-in/out for a specific userNotificationAnonymousSetting— Preferences for users identified only by phone (before app registration)MessageUserBlackList— Hard block for a specific user and message typeMessageOrganizationBlackList— Organization-level suppression of a message type for a user
Batch Messaging
For bulk campaigns,MessageBatch allows sending a single message type to a large list of recipients in one operation. Batch statuses:
created → processing → done / failed
Batch types include CUSTOM_CONTENT_MESSAGE (custom push/email/SMS content) and MOBILE_APP_UPDATE_AVAILABLE_MESSAGE_PUSH.
Remote Clients
Push notifications require a registeredRemoteClient — a device token stored for each resident’s device. Tokens are registered via SyncRemoteClientService when the resident app starts, and revoked via DisconnectUserFromRemoteClientService on logout.