Onboarding - the first 45 minutes with Panel

Slightly outdated UI - but still relevant!

Onboarding: The First 45 Minutes with Panel

These steps assume a CORE+DEPLOY license. If you have a different package, some steps may not apply. Approximate times are shown so you can pace yourself.

1. Log In and Set Up Two-Factor (3 min)

You’ll receive an email inviting you to log in. Only Google-powered email addresses (including Google Workspace for Education) can sign in.

• Go to my.k12panel.com and sign in with your Google email.
• Enter your cell number and save it, then log back in and confirm two-factor.
• You can enable an authenticator app now or later for stronger security.

2. Get Familiar with the Interface (3 min)

Panel is organized by the menu down the left side. As an administrator you see every menu item; other users see only what their role permits.

3. Configure Organization Settings (10 min)

Header color: in Settings, set a Header Background Color to make this org easy to recognize.

Google sync: open the Cloud Sync tab and click Authorize to grant Panel read-only access to your Google Workspace. This step must be performed by a Google Super Admin; if you aren’t one, invite a Super Admin under the Users tab and sign in as that user. After authorizing, a background sync begins and then repeats throughout the day.

Chromebook extension: in Settings → Software Downloads, follow the instructions to deploy the Chromebook extension in your Google Admin console. Deploy it at a high level of your organization so it reaches all users. It affects only district-owned Chromebooks, not the Chrome browser on PCs.

4. Install the Agent on a Windows Machine (5 min)

• In Settings → Software Downloads, download the custom Windows Agent Installer MSI to a thumb drive.
• Install it on a test Windows machine.
• The machine appears on your On-Ramp.

5. Adopt the Windows Machine (5 min)

• Find the new asset on the On-Ramp and adopt it.
• Reboot the test computer so it fully checks in.
• After check-in, the Asset is in Panel and ready to manage.

6. Choose and Configure a Software Package (15 min)

Build an Org Library: under Blueprints, add an Org Library named “Software.”

Join the Public Library: under Team Libraries, click Join Public Library so you can subscribe to prebuilt packages.

Subscribe to a Blueprint: under Team Blueprints, choose a package not already on your test PC (for example Google Chrome Enterprise, Adobe Reader, or Notepad++) and subscribe it into your Software library.

Build a Modifier: a Blueprint is generic; a Modifier is install-ready. On the new Blueprint, click Create New Modifier, name it (e.g. “Install Chrome”), leave the priority at default, and save. Some Blueprints expose properties to customize here; this one may have none.

7. Deploy the Package to Your Test Computer (5 min)

Modifiers reach Assets through Asset Groups.

• Build an Asset Group: under Asset Groups, create one named “Test Computers” and associate your new Modifier under Associated Asset-Scoped Modifiers.
• Add your test computer: open the Asset and use Add To Group to add it to “Test Computers.”
• Activate the computer: new Windows Assets start Inactive and are not affected by Modifiers. Click Activate.
• Force a poll: use the Command dropdown → Force Poll, right-click the Panel tray icon and choose System Poll, or simply reboot. After the poll, the software installs and an Asset Modifier Report tab appears showing the result.

8–10. People, Chromebooks, and Checkout

View People: by now your Google users should be imported under the People menu, organized by OU.

Map a Chromebook: log into a managed Chromebook (note the Chromebook Management Assistant extension running), then find it under Assets to see its location. A Chromebook reports accurate location only after running once with the extension.

Check out an Asset: open your test computer’s detail page and use Check Out to assign it to yourself. A Check In/Out history begins tracking the asset.

11. Next Steps

You now know the basics. Explore the rest of the documentation, and visit the training center at training.k12panel.com for videos across many topics.

Common Questions

Who must perform the Google sync authorization?
A Google Workspace Super Admin. Invite one under the Users tab if needed.

Why didn’t my Modifier install anything?
The Asset is probably still Inactive, or hasn’t polled yet. Activate it and Force Poll (or reboot).

What’s the difference between a Blueprint and a Modifier?
A Blueprint is the generic recipe; a Modifier is the install-ready, configured instance you deploy.

Does the Chromebook extension affect PCs?
No. It applies only to district-owned Chromebooks.

When will People appear?
Shortly after the first Google sync completes; give it a little time.