Invite Your Team to OpenFrame
Phase 1 — Account & Workspace Setup · OpenFrame Onboarding
OpenFrame is more useful with your whole team in it. Get your technicians invited now, so by the time devices start reporting in, everyone's already got access and the right role. It takes about two minutes.
Before you start
- You need an Admin role to add people.
- Have your team's email addresses handy. Ideally these match the identity provider you set up in Set Up SSO with Google or Microsoft — if SSO is on, invited users sign in with Google or Microsoft instead of a password.
Where to find it
Left nav → Settings → Employees & Permissions. This opens your workspace's user list, showing everyone's name, email, role, and status.
Invite people
- Click Add Users (top right). The Add Employees dialog opens.
- Type a teammate's address into User Email.
- Pick a Role from the dropdown (more on roles below).
- Adding more than one person? Click Add More Users to get another email + role row, and repeat. You can send a whole batch in one go.
- Click Send Invites.
Each person gets an email invitation to register. Until they accept, they show up in the list with an Invite status rather than Active.
No CSV upload today. If you've seen "bulk import a CSV" mentioned, note the current build doesn't have it — you add people by email, using Add More Users to queue several at once. For a big onboarding, just paste them in one after another.
Understanding roles
OpenFrame's user list shows two roles in play:
- Owner — the top-level account, typically whoever first stood up the tenant. Full control.
- Admin — full operational access to the platform.
When you send an invite, Admin is the role you'll assign. Owner and Admin are the two roles the platform offers today; if finer-grained, least-privilege roles matter to your shop, keep an eye on the console (role options may expand release to release) and see Managing Team Roles and Permissions (Phase 9).
Rule of thumb: give people the least access that lets them do their job. It's easier to grant more later than to walk back access after something goes sideways.
Reading the user list
The Status column tells you where each person stands:
- Active — they've accepted and can sign in.
- Invite Expired — the invitation lapsed before they accepted. Re-add them to send a fresh one.
- Deleted — the account's been removed; it stays visible for the record but can't log in.
To remove someone, click the ⋯ menu on their row and choose Delete. Do this the moment a technician leaves — it's the fastest way to cut off access, and pairs with your SSO offboarding.
A note on SSO + invites
If you turned on auto-provision during SSO setup, people on your domain can sign in without a manual invite — an account is created for them on first sign-in. That's convenient, but it means new accounts can appear without you adding them. Either way, swing by this page periodically to confirm everyone's role and status are what you expect.
Quick checklist
- Added each technician by email under Add Users
- Assigned a role to each
- Sent invites and confirmed they appear in the list
- Followed up on anyone showing Invite Expired
- Confirmed there are no stale or unexpected accounts
What's next
That's Phase 1 done — your workspace is configured, SSO is on, and your team is in. Next up is Phase 2 — Device Deployment: getting the OpenFrame agent onto your first macOS and Windows machines.
Based on OpenFrame v0.9.19. Screens and defaults may shift between releases — when in doubt, what's in your console wins.
