Skip to content

Notifications, Short Links & App Updates

Part of the Aashray Business Logic. Related: Accounts, Identity & Auth, Booking Lifecycle, Services, WiFi, Maintenance, Support & Gate.

This page covers member messages, staff-managed share links, and app version updates.

Notification channels

  • Aashray can attempt push notifications, email, and WhatsApp messages.
  • An event does not always use every channel.
  • When a member creates a booking, the system attempts email and WhatsApp messages for the attendee. If another member made the booking, the system also attempts messages for that person.
  • Booking status changes can trigger email, WhatsApp, or push messages, based on the status path.
  • Password recovery, maintenance updates, and WiFi request updates also use selected notification paths.
  • A notification failure does not undo the booking or service request.

Push notifications

  • The member app registers a phone push address while it runs on a physical device.
  • The app sends the current push address to the backend at sign-in.
  • The app clears the stored address when the member signs out through the supported sign-out path.
  • Tapping a push notification opens the app screen named by that notification. The destination can be a booking or another supported screen.

Staff can create short links for accounts, rooms, cards, food, Adhyayan, travel, Utsav, and WiFi resources. An active link redirects a person to its full resource page.

  • Staff can create, enable, disable, edit, and delete links.
  • Staff can filter links by department.
  • Staff can view the number of times each link was opened.
  • The staff panel can create share links for Adhyayan and Utsav group resources during event management.
  • Each department has its own staff permission rule for link management.

The member app does not use the short-link screen as a general tutorial directory. The staff panel owns short-link management.

App updates

  • At startup, the member app checks its installed version against the latest version set by staff.
  • The update record can include release notes, a store link, and a required-update flag.
  • A required update blocks normal app use until the member updates.
  • An optional update can be delayed until the next local midnight.
  • This process updates the whole app. It does not turn individual features on or off for selected members.

Known limitations today

  • The backend refreshes a member's phone push address at sign-in. A new device can stop receiving push messages until the member signs in again.
  • Some automatic alerts use fixed recipient lists. Staff cannot change these recipients in the panel.
  • A notification can fail without a member-facing recovery step.