Assign Devices to a Customer
Phase 2 — Device Deployment · OpenFrame Onboarding
A device in OpenFrame belongs to a customer (the client org you set up in Phase 1). Getting that assignment right is what keeps a 200-endpoint fleet organized by client instead of one undifferentiated pile. The key thing to know: assignment happens at enrollment, baked into the install command.
Before you start
- You need an Admin role.
- You've created the client org already (Set Up Your Customer Organizations, Phase 1).
How assignment actually works
When you generate an install command, it carries an --orgId that ties the agent to a specific customer. So a device isn't "moved" into a client after the fact — it enrolls directly into the customer you chose when you generated the command. Pick the right customer before you run the installer and the device shows up in the right place from its first check-in.
Devices enrolled without a specific customer land in the Default org. If you see things accumulating in Default, that's the signal someone deployed with a generic command instead of a customer-scoped one.
Enroll a device into a customer
Two equivalent paths:
From the customer: open the client on the Customers page → Devices tab → Add Device. The New Device screen opens with Select Customer already set to that client.
From Devices: go to Devices → Add Device, then use the Select Customer dropdown to choose the client.
Either way, on the New Device screen:
- Confirm Select Customer is the right client.
- Choose Select Platform — Windows or macOS.
- Optionally Add Device Tag to label it (Phase 2, Organize Devices with Tags).
- Use the generated Device Add Command — Copy Command to run it on the target machine, or Run on Current Machine for the one you're on.
The command includes the server URL, an enrollment key, and the --orgId for that customer. When the agent installs, it reports straight into that client.
If antivirus blocks the install, it's a known false positive — add the listed OpenFrame folders (e.g.
C:\Program Files\OpenFrame,C:\Program Files\TacticalAgent) to your AV exclusions, as the installer screen notes.
Verifying
After it checks in, the device's detail page shows its Customer (Site) near the top — confirm it reads the right client, not Default. You can also open the customer → Devices tab and see it listed there.
Quick checklist
- Picked the correct customer before generating the command
- Generated the install from the customer's Add Device (or chose it in Select Customer)
- Ran the customer-scoped Device Add Command on the endpoint
- Added AV exclusions if the install was blocked
- Confirmed the device's Customer (Site) is the right client, not Default
What's next
Your devices are landing under the right clients. For a fuller tour of the per-customer view and how the org hierarchy works, see Organizations & Multi-Tenancy Overview (Platform Navigation).
Based on OpenFrame v0.9.19. Enrollment flags and the install command evolve between releases — what's on the New Device screen wins.
