OpenFrame Gen1 is Here

OpenFrame

Configure Your Notification Preferences

BEST PRACTICESCONFIGURATIONGUIDEIMPLEMENTATIONMONITORINGOPENFRAME

Phase 1 — Account & Workspace Setup · Step 4

Section

June 18, 2026

Published

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Configure Your Notification Preferences

Phase 1 — Account & Workspace Setup · OpenFrame Onboarding

Read this first. OpenFrame doesn't yet have a single "notification preferences" screen where you set per-user severity floors and choose delivery channels in one place — a unified notification & alert center is on the roadmap. Until it ships, the controls that decide what reaches you and where live in a few different spots. This guide shows you the levers that exist today so you're not waiting on clients to call you. We'll update it to a straight click-through once a dedicated preferences page lands.

The goal of this step is simple: make sure the right alerts reach the right people, and the noise doesn't. Here's how to get there with what's in the product now.

Before you start

  • You need an Admin role.
  • That's it — everything below is in the OpenFrame console itself; there's nothing external to connect.

The three levers that control your notifications today

1. The Notification Center — where alerts reach you

The bell icon in the top navigation bar is your live notification hub. Click it to open the Notification Center, a side panel with two tabs: New Notifications (your live queue) and Notifications History (a searchable record, kept for 30 days).

The most common item you'll see is an Approval required card — Mingo asking permission to run an action you've gated. You can Show Command to see exactly what it wants to run, clear items with the checkmark, or use Complete All to clear the queue.

Two toggles at the bottom of the panel control how loudly it reaches you:

  • Show Notifications — pop-up messages for new items as they arrive.
  • Desktop Notifications — alerts even when the OpenFrame tab is in the background, so a waiting approval doesn't stall while you're working elsewhere.

If you bounce between tools all day, turn on Desktop Notifications so nothing waits unseen. Full walkthrough: Understanding the Notification Center (Phase 10).

2. AI approval prompts — Mingo and Fae asking permission

A big share of what you'll "get notified" about isn't a failure — it's your AI agents asking before they act. Anything you've set to Ask User or Ask Technician in AI Settings & Guardrails surfaces as an approval request (in the Notification Center) rather than running silently.

So your guardrail settings are a notification setting: tighten them and you'll be pinged more often (more control, more interruptions); loosen them and agents handle more on their own (fewer pings, more trust). Tune this deliberately — see Configure Your Tenant Settings for the walkthrough.

3. Monitoring severity — deciding what's even worth an alert

What counts as "worth telling you about" starts at the Monitoring layer. Each monitoring policy carries a severity, which is your basis for deciding what should escalate versus what's just logged. Getting severity right on your policies is how you set a de facto "floor" today — only the things you care about get flagged loudly.

You'll build these out properly in Phase 4 — Monitoring & Policies. For onboarding, just know that severity is set on the policy, not in a global preferences page.

A sensible day-one setup

You don't need to perfect this now. A good starting point:

  1. Open the Notification Center (bell) and turn on Desktop Notifications so approvals don't wait unseen.
  2. Leave the default AI guardrails in place (destructive actions ask first), and adjust only where your comfort level differs.
  3. Come back in Phase 4 to set severities on your monitoring policies so the important stuff stands out.

That gets you real-time alerts and AI approvals from day one, without drowning anyone.

What's missing today (and coming)

So you know where the edges are: there's currently no single screen to set per-user severity floors, toggle email digests, or route notifications to external channels or webhooks. Those are part of the planned notification/alert center. If a unified preferences page is important to your workflow, it's worth a vote/feature request in the OpenMSP community.

Quick checklist

  • Opened the Notification Center (bell) and set Show / Desktop Notifications to match how you work
  • Reviewed AI guardrails so you're pinged for the right approvals (Tenant Settings guide)
  • Noted that monitoring severity (Phase 4) is where you'll tune what escalates
  • Flagged any need for a unified preferences center to your OpenFrame contact

What's next

That wraps Phase 1. Next up is Phase 2 — Device Deployment: getting the OpenFrame agent onto your first machines so there's something to actually monitor and alert on.

Based on OpenFrame v0.9.19. This area is actively evolving — re-check the console and roadmap before treating any of it as fixed.

Vladislav Marchenko

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.

More in Phase 1 — Account & Workspace Setup

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.

AI MSP

Start with a readiness assessment, not a tool purchase. Confirm your ticket history is clean and your RMM, PSA, and monitoring systems connect. Then pick one high-volume, low-risk workflow, usually ticket triage, and pilot it on internal tickets before any client sees it.
Automate high-volume, low-risk tasks first. Ticket triage and alert noise reduction top the list because they run constantly and a human still resolves the underlying issue. Save security approvals, billing changes, and client-facing actions for later, always with a human in the loop.

AI Safety

It can be, with governance. Keep a human in the loop on high-risk actions, log every automated step for audit, and choose platforms that keep your data yours with no vendor lock-in. Pilot on internal data first so you catch issues before client systems are involved.

AI for MSPs

Set a baseline before rollout, then track tickets closed per technician, mean time to resolution, percentage of tickets resolved with no human touch, technician hours reclaimed, and cost per ticket. AI-driven automation commonly cuts operational cost per ticket by 25 to 40%.

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.

Zabbix for MSPs

Yes. Zabbix is open source under GPLv2 with no license fee, no per-device pricing, and no paywalled features. You can monitor unlimited hosts at zero software cost. The real expense is the infrastructure to host it and the engineering time to configure and maintain it.

Log Aggregation

Yes. Self-hosted Loki is free and open source under the AGPLv3 license, so you pay only for the infrastructure you run it on. Grafana Cloud is the paid, managed option, starting at $0.45 per GB of logs ingested with 50 GB free each month.

MSP Password Manager

There is no single best. For most MSPs, Bitwarden balances low cost and no lock-in, 1Password offers the most polished multi-tenant console, and Keeper adds built-in privileged access. The right pick depends on your budget, client base, and need for PAM.