OpenFrame is on your phone now!

Understanding the Notification Center

DOCUMENTATIONGUIDEOPENFRAMEPLATFORM UPDATESUSER EXPERIENCE

Phase 10 — Ongoing Operations · Step 1

Section

June 24, 2026

Published

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Understanding the Notification Center

Phase 10 — Ongoing Operations · OpenFrame Onboarding

The bell in the top-right corner is mission control for anything that needs your attention — Mingo asking permission, alerts firing, status changes. This guide covers what lives there and how to keep it from becoming noise.


Open it

Click the bell icon in the top navigation bar (a small dot on it means you have unread items). The Notification Center opens as a side panel with two tabs: New Notifications and Notifications History.


New Notifications

This is your live queue. The most common item you'll see is an Approval required card — that's Mingo asking permission to run an action you've gated in your guardrails (Phase 9). Each card lets you:

  • Show Command — expand to see exactly what Mingo wants to run before you decide.
  • Acknowledge / complete (the checkmark) — clear the item once you've handled it.

Use Complete All (top of the panel) to clear the whole queue at once when you've worked through everything.

Approval cards here are the same ones that appear in ticket chats (Phase 6). The Notification Center just gives you a single place to catch them, wherever they originated.


Control the noise

At the bottom of the panel are two toggles:

  • Show Notifications — show pop-up messages for new alerts as they arrive.
  • Desktop Notifications — notify you even when the OpenFrame tab is in the background, so you don't miss an approval while working elsewhere.

Tune these to your workflow. If you live in OpenFrame all day, in-app pop-ups may be enough; if you bounce between tools, turn on desktop notifications so a waiting approval doesn't stall automation.


Notifications History

Switch to the Notifications History tab for a searchable record of past notifications — handy for "did that approval go through?" or tracing a status change. Use the Search for Notification box to filter.

Retention: history is kept for 30 days, then permanently deleted. If you need a longer-lived record, the Logs page (Phase 9) and ticket history are your durable trail.


Quick checklist

  • Opened the bell → Notification Center
  • Reviewed New Notifications and used Show Command before approving
  • Cleared items (checkmark) or Complete All
  • Set Show / Desktop Notifications to match how you work
  • Knew to check Notifications History (30-day retention) for past items

What's next

You know how to stay on top of what needs attention. Next, keep the agent itself healthy: Managing the OpenFrame Client — Updates & Recovery.


Based on OpenFrame v0.9.19. The Notification Center evolves between releases — what's in your console wins.

Vladislav Marchenko

Head Of Marketing

Hi all! My name is Vlad and I’ve been brought on to head the marketing team at Flamingo. Thankfully, this isn’t the first time I will be building a marketing department from scratch, so the experience should come in handy. Now it’s time to dive into the world of MSPs and find myself in this new world.

Related Content

Product Releases

Webinars

Case Studies

Blog Posts

Frequently Asked Questions

MSP AI Agents

Yes. In production MSP shops today, 10% to 25% of tickets close before a human opens them. Thread alone has processed 173 million tickets across 750-plus MSP partners at 96% triage accuracy, handing back 490,000-plus technician hours. Agents own the low-risk, high-volume work (password resets, MFA enrollment, known installs, onboarding and offboarding) and flag anything that touches production data or needs judgment for a human to take.
On a five-person desk, reported deployments show $78,000 to $130,000 in annual direct labor savings, roughly 30% fewer escalations, and 15% to 20% better SLA compliance. Broader MSP adoption data adds ticket handling time cut by 45% and five to 12 points of margin, all from reclaimed capacity rather than headcount cuts.

Getting Started

The People Hub is Flamingo's internal home for the team. Every employee can browse the team roster, open a colleague's “Who Am I” profile, share what they shipped each month, and keep their own profile up to date. Managers additionally see performance insights built on the SPACE framework.

About OpenFrame

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.
Nine, per Ivanti's own End of Life index: Cherwell Service Management, Cherwell Asset Management, Service Desk (Powered by LANDESK), Desktop & Server Management, Endpoint Security (Powered by HEAT), PatchLink, Workspace Control, Virtual Desktop Extender and Browser Manager. DSM 2026.1 is the sharpest case, since it shipped on 13 January 2026 and loses full support in December of the same year.
Releases 22.7, 22.8, 25.1.0.x, 25.1.1.x and 25.1.2.x all end support on 31 January 2027. Only 25.1.3.x reaches 30 April 2027. Staying current also means a hardware purchase: Ivanti states that ICS 25.1.2.x runs only on new ISA 6500 and ISA 8500 hardware, with 25.1.3.x and later adding supported virtual and cloud environments.
It is the total power a switch can supply across all its ports, which is almost always less than ports times the per-port maximum. Add up the device draws at their IEEE class: 802.3af phones at 12.95 W, 802.3at access points and cameras at 25.5 W, 802.3bt devices at 51 W or 71.3 W. Add 20% headroom and buy a switch whose total budget exceeds that figure.
A legal hold pauses deletion for mailboxes or messages relevant to actual or anticipated litigation. In Microsoft 365, litigation hold covers a whole mailbox and an eDiscovery hold can be scoped by query or custodian; both stop automated purging and keep original versions of edited items. The hold has to be applied before the content is deleted, so it belongs on the offboarding checklist ahead of account removal.
For a single site with under a hundred devices, plan a day on site for discovery and the wireless survey, a week of passive counters for performance, and two days for the scan review and the report. Multi-site and heavily segmented networks scale roughly with the number of subnets, since each one needs its own discovery pass.
A one-page executive summary, the inventory and topology diagram, findings grouped by severity with evidence for each, a roadmap with costs and dates, and an appendix of raw scan output. Each finding carries what was found, the evidence, the risk, the fix, the cost, the owner and a target date.