Managing Alerts in the e-Pragati Mobile App Notification Settings

The e-Pragati mobile application serves as the front door to one of India's largest e-governance platforms, giving officers, programme managers, and citizens a single pane for service requests, approvals, and identity workflows. Like Australia's myGov app or the Australian Taxation Office's mobile companion, it surfaces service updates, security warnings, and workflow events through a configurable alert layer that can either help you stay current or drown you in pings. Users who understand how to shape this layer spend far less time triaging irrelevant notifications and far more time acting on the items that genuinely matter.

With dozens of department agencies and programme modules feeding into one inbox, the default configuration is rarely ideal for anyone. From Sydney's Western Sydney offices coordinating cross-border IT projects to Canberra's APS staff benchmarking international platforms, many Australian readers will recognise the challenge of alert fatigue in shared digital services. This reference walks through the practical controls, hidden toggles, and integration considerations that make daily notification management straightforward, regardless of whether you are an Indian government employee or an Australian professional comparing platform design.

Understanding the Notification Architecture

The app's alert engine sits between the central e-Pragati platform and your device's operating system. When a service event occurs - a workflow approval, an uploaded document, an identity verification request, or a security incident - the platform publishes a structured message that the mobile client translates into a notification. Each module can fire its own category, which is why an auditor's daily summary can look so different from a citizen-facing service update within the same application.

Channels matter as much as categories. The app supports three delivery routes: in-app banners for active sessions, push notifications for background delivery, and email or SMS digests for critical events. Australian organisations with field staff in remote Queensland or Pilbara deployments will appreciate that the SMS fallback works even on the most basic regional mobile networks, similar to how the Australian Taxation Office uses SMS to reach users outside major coverage areas where push delivery may be unreliable.

One feature often overlooked is the priority tagging system. Critical alerts - those marked as compliance, security, or payment related - bypass quiet hours automatically. This mirrors design choices seen in the Australian Cyber Security Centre's guidance for mission-critical systems, where essential warnings must reach the operator regardless of suppression rules. Less urgent items, such as newsfeed updates or training reminders, sit lower in the queue and respect the user's chosen schedule.

Accessing Notification Settings on Android and iOS

Open the app and tap the profile avatar in the upper right corner. From the slide-out panel, choose Settings, then Notifications. On Android 10 and later, the menu sits within an "App Settings" subfolder; on iOS, it is integrated directly under the main settings list. First-time users will see a welcome screen explaining the four broad alert groups and the priority tiers behind them.

Before adjusting in-app preferences, it is worth confirming that the device-level channel is not blocked. On Android, this means navigating to Settings → Apps → e-Pragati → Notifications. On iOS, the path is Settings → Notifications → e-Pragati. Many users in Adelaide and Hobart report that corporate-managed devices enforce blanket restrictions through MDM policies, in which case only the system administrator can grant notification rights. If the toggle is greyed out, contact your IT helpdesk rather than assuming the app is at fault.

Once inside the notification hub, the layout follows a familiar pattern: a master toggle, per-category switches, sound and vibration selectors, and a quiet hours schedule. Power users in Melbourne's enterprise architecture community, who often document similar UX patterns for shared platforms, may find value in reviewing the enterprise architecture decisions reference maintained alongside this blog, as it captures the design rationale behind the category groupings and priority weights.

Alert Categories and Their Meanings

The app distinguishes between six alert families, each colour-coded in the inbox view. Service requests cover anything triggered when you lodge or update a service ticket. Workflow notifications relate to approvals, escalations, and task assignments. Identity and security events include login attempts, password resets, and biometric verifications, and they are flagged with a shield icon in the inbox summary.

The fourth family, programme updates, delivers news about scheme revisions, training opportunities, and policy memos. These are typically the most numerous, and they are the group most Australian systems administrators disable when they are using the app for benchmarking purposes during short-term assignments. The fifth family covers payments and receipts, which Australian users should leave enabled even if everything else is muted - missed financial confirmations are harder to reconcile after the fact and may trigger downstream reconciliation issues. The final family, system messages, includes app version updates and scheduled maintenance windows.

Knowing which family fires each ping helps in two ways. First, it lets you mute the noisy groups while preserving the meaningful ones. Second, it aids in writing ticket descriptions to support teams, since the category name often tells them which subsystem generated the alert and who is responsible for investigating. Brisbane-based IT support teams frequently ask users to include the category name in their first message, which speeds up triage considerably.

Customising Push, Email, and SMS Alerts

Push notifications are the most battery-sensitive channel, but they are also the most immediate. For each of the six alert families, you can choose between three delivery modes: real-time push, batched digest, or off. A useful pattern, often recommended by digital transformation leads in Brisbane and Perth consulting firms, is to enable real-time only for security and payment categories, batch all others into a morning and evening digest, and disable programme updates entirely.

Email digests draw from the same categories but offer an extra layer of granularity. Within the email preferences, you can include or exclude attached PDFs, choose between plain text and HTML, and opt into a weekly executive summary. The SMS channel is reserved for the four highest-priority event types and cannot be fully disabled, which aligns with the Australian government's stance that critical service messages should always reach users, even when mobile data is unavailable on a regional network in the outback.

Users juggling multiple roles - for example, an employee who is also a service beneficiary - can set per-role overrides. This is configured under Settings → Account → Role Switcher → Notification Profile. Each profile retains its own preferences, so switching from "Department Officer" to "Citizen" instantly reshapes the alert stream without manual toggling. The app remembers the last profile used and offers to switch back when it detects context clues, such as a specific IP range or geofenced office location.

Do Not Disturb and Quiet Hours Configuration

Quiet hours prevent non-critical alerts from interrupting meetings, sleep, or weekend downtime. The setting accepts two schedules: weekday and weekend. Australian professionals working across IST and AEST time zones will be relieved to find that the schedule respects the device's local time, so a 10pm Adelaide quiet window silences evening push notifications even though servers run on Indian Standard Time.

Critical alerts - security incidents, payment failures, identity verification requests - still pass through quiet hours. If you need complete silence during a defined window, for instance when presenting at a Canberra conference, the Focus Mode integration on iOS or the Do Not Disturb shell on Android can suppress even these. The app respects these system signals, displaying a small moon icon in the status bar so you know the override is honoured and that critical pings have been queued rather than lost.

For shift workers in regional Western Australia or the Northern Territory, the app offers a recurring roster option. You can upload a calendar feed in ICS format and the app will compute quiet windows automatically. This is particularly useful for fly-in fly-out staff who alternate between site days and home days and want their alert schedule to follow them without manual adjustments at every rotation.

Troubleshooting Missed or Delayed Notifications

If notifications stop arriving, work through a short checklist. First, confirm the device is online and that background data is permitted for the app. Second, verify that the app is not in a battery-optimisation whitelist exclusion that kills background activity on Android. Third, check that the account has not been logged out from another device, which pauses push delivery until re-authentication. Brisbane-based IT support teams often resolve most cases at this third step alone, since a stale token is the most common silent failure.

Push delivery can also be affected by corporate firewalls, especially in agencies that proxy all traffic through a single egress point. If the app appears in your recent activity but no alerts have surfaced for several hours, force-closing and reopening it triggers a manual sync that often clears the backlog. This is the same recovery pattern recommended for the Australian Government's myGovID app when users face similar stalls in identity-related push flows.

When the issue persists, open the in-app help widget and tap "Run Diagnostics". The tool tests push token validity, server reachability, and account state, returning a short report that you can attach to a support ticket. Security professionals who need a deeper understanding of the underlying transport can review the cybersecurity frameworks reference to see how alert delivery fits into a wider defensive posture across government platforms.

Privacy, Security, and Battery Considerations

Notifications contain excerpts of personal data - names, ticket references, partial account numbers - and they can be visible on a locked screen. The app offers a "Hide sensitive content" toggle under each category, which replaces the alert preview with a generic "New alert from e-Pragati" string. This is particularly valuable for users in shared offices in Melbourne's CBD or on public transport across Sydney's train network, where shoulder-surfing is a real risk that can expose service details to unintended observers.

Battery impact correlates with how many categories are enabled for real-time push. Each active stream holds a small socket open to the notification gateway. Users who want maximum endurance on a single charge, such as field officers travelling between Perth and Broome on multi-day assignments, should batch as many streams as possible into the morning and evening digests. The trade-off is a slight delay in receiving less critical updates, which most users find acceptable in exchange for a device that lasts the working day.

From a security standpoint, treat the notification stream as an audit log. Review the alert history weekly, flag any unfamiliar login attempts, and enable the optional biometric prompt for sensitive transactions. The Australian Cyber Security Centre's Essential Eight framework emphasises similar behaviours, and adopting them within e-Pragati complements rather than replaces your home agency's broader controls, including the Notifiable Data Breaches scheme obligations that apply to Australian organisations handling personal information.

If you manage alerts through the e-Pragati mobile app and want a deeper dive into how these design choices compare with Australian government platforms, explore the related references on this site and subscribe to the newsletter for weekly updates on digital governance, enterprise architecture, and ICT management.