--- title: Notifications order: 4 updated: 2026-05-28 --- # Notifications Intigra notifies you when things happen in the app that you might care about — a new enquiry arrives, a quotation is sent, an enquiry is marked lost, your password is changed, and so on. You decide *which* events notify you and *how loud* each one is. ## Open the settings 1. Open *Settings* in the sidebar. 2. Pick *Personalisation*. 3. Under *Notifications*, click *Notification Preferences*. ## The four modes Every notification event has a mode. You can change the mode for each event independently. - **Enabled** — Notification appears as a toast in the app *and* as a push to your phone (even when the app is closed). Best for things you must not miss. - **In App** — Notification appears as a toast while you have the app open, and stays in the history list. No phone push. - **Silent** — Notification quietly lands in the history list. No toast, no phone push. Use this when you want a paper trail but no interruption. - **None** — Notification is dropped completely. Not saved, not sent anywhere. Use this when an event is genuinely irrelevant to you. If you have not picked a mode for an event yet, it uses its default — shown in the dropdown as *Enabled (default)*, *In App (default)*, etc. The default is sensible per event (sign-in alerts default to *Enabled*; bulk-traffic events like "new enquiry added" default to *In App*). ## The tabs The Preferences modal is split into tabs by area: - **General** — events that apply to every user: sign-in alerts, password change, email change. - **Enquiry** — events tied to the enquiry / quotation workflow: a new enquiry is added, an offer is queued or sent, an enquiry is converted to a sales order, an enquiry is marked lost or deleted, a quotation follow-up is sent. - **Purchase** — procurement-side activity: an RFQ is released to suppliers, a vendor follow-up email goes out, a vendor submits (or revises) a quotation, a purchase order is sent to a supplier, a PO follow-up is sent. RFQ-related rows need *procurement.viewAlreadyPlacedEnquiries*; PO-related rows need *procurement.viewAlreadyPlacedPurchaseOrders*. - **Inventory** — stock movement: a stock arrival voucher is created or approved, a stock delivery voucher is created or approved. These notifications are **scoped to the godowns you manage** — if a voucher touches a godown you don't have in *inventory.manageGodownScope*, you won't be notified about it. Admins receive regardless. - **HR** — vouchers and leave: a junior submits an expense or travel voucher (seen by users with *expense.viewAllExpenses*); your own voucher is approved (sent to you, the submitter); a junior applies for leave (seen by *attendence.viewAllLeaveApplications*); your own leave is approved (sent to you, the applicant). All Purchase, Inventory, and HR events default to *None* — opt in via the dropdown for the ones you want to hear about. You only see events you have permission to act on. For example, "When an enquiry is added" only shows for users with *enquiry.view* permission. If a row should be there but isn't, ask your administrator about your permissions. ## How notifications reach you Every notification stays in the **history** for 90 days regardless of mode (except *None*, which is never stored). While you have the app open — web, desktop, or mobile — *Enabled* and *In App* events show a toast and appear in the bell with an unread badge. On the mobile app specifically, *Enabled* events also fire an OS-level push (the same kind of notification WhatsApp or Gmail sends) so you see them on your lock screen even when the app is closed. The first time the app starts after a fresh install, it asks for permission to send these — pick *Allow*. To stop receiving them, change the event's mode to *In App* or *Silent*. When you have both a PC and your mobile signed in to the same account, both receive the toast in parallel. *Enabled* mode does not push to your phone when the app is already open and connected — the in-app toast is sufficient. ## The notification history Click *Notification History* on the same screen to open the history list. - **Tap a row to jump to the related screen.** A notification about an enquiry takes you to that enquiry; a sign-in alert takes you to *Security*. Rows that don't link anywhere are flagged by a missing chevron. - **Filter by Tab** to narrow to a single area (Enquiry, General, etc.). - **Filter to *Unread only*** if you want to clean up the unread badge. - **Right-click (or hold) a row** to mark it read / unread or delete it. - **Clear All** wipes every notification that matches your current filters. This is permanent. The history only ever keeps the **15 most recent notifications per user**. Older rows are pruned automatically as new ones arrive — so the bell stays fast to open and the unread badge stays meaningful. If you need a permanent paper trail of a specific event, jump to its linked screen (enquiry, voucher, etc.) where the underlying record stays intact. If you mark something read on one device, the badge updates on your other device within a second. No refresh needed. ## Common questions ### Why didn't my phone get an OS notification? A few possibilities. (1) The event's mode is set to *In App* or *Silent* — change it to *Enabled*. (2) You denied notification permission when the mobile app first started — open the phone's *Settings* → *Notifications* → *Intigra* and allow notifications. (3) The mobile app was already open and connected — in that case the app received the toast in-app and didn't duplicate it as an OS push. ### Why is "When an enquiry is added" not in my list? You probably don't have *enquiry.view* permission. Talk to your administrator if you should. ### Will I get the same notification twice — once on my PC and once as a phone push? No. If your phone has the app open and connected, the system sends the toast in-app and skips the phone push. If your phone is offline (app closed or backgrounded long enough that the connection dropped), only then does Intigra fall back to OS push for *Enabled* events. ### Can the notification history get too long? No — the history is capped at the 15 most recent notifications per user. As new notifications arrive, the oldest ones are dropped automatically so the bell never piles up. (Stale rows beyond 90 days are also pruned as a fallback.) You can also use *Clear All* (with filters) to wipe rows on demand.