Organizations & Multi-Tenancy Overview

Reviewed 24/09/2026
Platform Navigation · OpenFrame Onboarding

OpenFrame is built for MSPs, which means it's multi-tenant from the ground up: your work is organized by customer (client org). This guide is the orientation — how customers map to clients, how to read the Customers area, and how to live inside a single client's view. (For creating customers, see Set Up Your Customer Organizations, Phase 1.)

The mental model

• A customer is one of your clients.
• Every device, ticket, and log belongs to a customer.
• A built-in Default customer catches anything enrolled without a specific client assigned.

Once you internalize "everything belongs to a customer," the whole platform makes more sense — filters, tickets, and policies all hang off this structure.

Reading the Customers list

Open Customers from the sidebar. Each row shows the client's device count, user count, and last activity — a quick health read across your whole book of business. Tabs split Active from Archived, and Search finds a client fast once you have a lot of them.

Working inside one customer

Click a customer to drop into its scoped view. Everything narrows to that one client across four tabs:

• Devices — only this client's machines (with the same search, tags, and Add Device you get globally).
• Tickets — this client's tickets.
• Logs — this client's activity feed.
• Details — the client's profile (name, website, address, notes, logo).

Plus Edit Customer and Archive Customer up top. Think of it as a focused console for that single client — handy when you're heads-down on one account.

How it connects to the rest of the platform

This structure quietly powers things elsewhere:

• Devices carry their Customer (Site) on the detail page, so you always know whose machine you're on.
• Compliance policies apply down a hierarchy — Agent → Site → Client → Default — with inheritance, so you can set a baseline at the client level and override per device (see Device Compliance & Evidence, Phase 9).
• Tickets and logs stay attributable to the right client for clean reporting and accountability.

Quick checklist

• Understood that devices, tickets, and logs all belong to a customer
• Read the Customers list (device/user counts, last activity, Active/Archived)
• Opened a customer and toured its Devices / Tickets / Logs / Details tabs
• Knew the Default customer is the catch-all for unassigned devices
• Saw how the customer hierarchy feeds device assignment and policy inheritance

What's next

You know how the platform is organized by client. To make sure new machines land in the right one, revisit Assign Devices to a Customer (Phase 2); to set client-level policy and read compliance, see Device Compliance & Evidence (Phase 9).

Based on OpenFrame v0.9.19. The multi-tenancy model evolves between releases — what's in your console wins.