Deploying Blank

Blank is a managed extension. An administrator installs it through browser management and supplies enrollment settings; employees do not need a Blank account. Start with a dedicated test device or group and confirm reporting before expanding the rollout.

Before you start

Sign in at /admin/ and create an organization on Free if you do not already belong to one.
Review workplace notices, the Privacy Policy, and any required DPA.
Open Deployment for installation and enrollment settings. Owners and admins can see the organization token; treat it as a deployment secret.
Confirm the relevant store serves the approved production extension, version 0.1.0 or later. The old 0.0.1 permission spike is not the production product. As of 3 October 2026, the recorded production submissions are awaiting store review; contact support to confirm availability before rollout.

Installation and enrollment are separate. The production build needs both orgToken and apiBase, with the API base set to https://useblank.dev. Installing an extension alone does not connect it to your organization.

Select Google Admin · Chrome, Intune · Edge (Windows), or Jamf Pro · Chrome (macOS). Your platform selection stays in the page link. Copy each installation/enrollment artifact into the corresponding management setting; if copying fails, use the displayed error to retry. Read-only members cannot retrieve the organization token or complete a deployment configuration.

Chrome through Google Admin

Chrome Web Store ID: fmafngfpamnpcppklklfphbmoblbjaii.

In Devices → Chrome → Apps & extensions → Users & browsers, select your test organizational unit. Add Blank by its Chrome Web Store ID and choose Force install.
In Blank's Policy for extensions, paste the enrollment JSON from Deployment → Google Admin · Chrome and save. Google Admin uses a Value envelope around each value:
```
{
  "orgToken": { "Value": "YOUR_ORG_TOKEN" },
  "apiBase": { "Value": "https://useblank.dev" }
}
```

These values belong in the extension's policy editor. They are not a nested ExtensionSettings.policy browser policy.

Edge through Intune on Windows

Edge Add-ons ID: dnmoeacnpkkkkkglcholcidhiaccjjoj.

In the Windows Settings catalog → Microsoft Edge → Extensions → Control which extensions are installed silently, add the installation entry from Deployment → Intune · Edge (Windows). It uses the Edge update URL https://edge.microsoft.com/extensionwebstorebase/v1/crx. Preserve existing entries and assign only to your test group.
Deliver the separate enrollment script from the dashboard to the same group as an Intune Windows platform script. Use system context and a 64-bit PowerShell host, following your script-signing policy. It writes orgToken and apiBase as strings under HKLM\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\dnmoeacnpkkkkkglcholcidhiaccjjoj\policy.

The enrollment script does not install the extension. A Chrome policy or Chrome Web Store update URL is not the Edge installation path.

Chrome through Jamf on macOS

Use Deployment → Jamf Pro · Chrome (macOS) for two complete plists:

Browser installation settings in preference domain com.google.Chrome. Merge the Blank entry with the existing ExtensionInstallForcelist rather than replacing other extensions.
Enrollment settings in the separate preference domain com.google.Chrome.extensions.fmafngfpamnpcppklklfphbmoblbjaii.

Scope both to the same test Macs. Enrollment belongs in the extension preference domain, not inside the browser installation settings.

Verify installation and enrollment

Policy delivery depends on your management tool, device connectivity, and browser check-in schedule. Installation and enrollment can arrive separately; saving settings does not prove they reached a device.

The Deployment status panel distinguishes all enrolled devices from devices that checked in during the last 24 hours and shows reported extension versions. It refreshes automatically. On a connection failure, the last successful result stays visible with recovery controls; it is not a fresh check-in. Open Device not appearing? for troubleshooting.

Inspect chrome://policy or edge://policy. Confirm the installation entry and Blank's orgToken and apiBase have reached the device.
Check that the installed extension is the production version and shows enrollment in the intended organization.
In Deployment, confirm the device appears and its version is shown. On that test device, open an organization-permitted AI tool in Blank's catalog. Choose Check recorded visits to verify activity in All events; no sensitive test submission is needed. Keep the browser online and refresh if the visit has not arrived. Overview totals update every 5 minutes. Registration and activity reporting are different; the seat count updates hourly.
Confirm the managed user cannot disable or remove the extension. On the test device, remove the force-install assignment and verify uninstall behavior before expanding the rollout.

Measure admin work and natural propagation separately. Record any manual policy reload or browser restart; do not treat an assisted refresh as the natural delivery time.

Every organization starts in Monitor mode. Coaching and blocking require deliberate activation after 14 days of real monitoring data. Network blocking also requires a policy installation and a matching blocking policy. See policy and enforcement for the gates.

For enrollment problems or a token change, use deployment support. Do not email your organization token.

View this page as Markdown →