Web Dashboard

1. Go to producergrid.com/register.
2. Enter your email address, choose a password, and optionally add your name.
3. Click Create Account.
4. Check your email for a confirmation link. Click it to verify your email address.
5. Sign in at dashboard.producergrid.com/login.

After confirming your email, you'll create your organization - the container for all your workstations, plugins, and licenses.

1. On first login, you'll see the Create Organization screen.
2. Enter your organization name (e.g. your studio name or company).
3. Choose a plan: Free (up to 2 workstations) or Pro (unlimited).
4. Click Create. Your organization is ready.

You can change the organization name and plan later in Settings → General.

The status bar at the top of every page is the fleet at a glance. Each figure is a link to the page it summarises:

• online - machines reporting now, out of the machines enrolled
• plugins - distinct plugins across the fleet, with the crashed count beside it when any failed validation
• DAWs, Custom Presets, libraries, samples, projects, equipment - fleet-wide counts
• Rescan - asks every online machine for a fresh scan

The Home page below it holds the workstation cards, the licence and project summaries, and the alert feed.

Every plugin installed anywhere in the fleet, one row per plugin (name and vendor), with the formats it was found in.

• Filter chips - No License, Flagged, Blocked, Whitelisted, Outdated, Crashed. Each carries its own count, and only the ones your organization actually has appear: policy chips need a policy, Outdated needs a known newer version
• Vendor, format, machine and category - four selects beside the chips
• The line above the table always names what is filtering, and Clear filters removes all of it, search included
• Map - the plugin × machine grid: which machines have each plugin, and which version
• Export CSV - the filtered list, as you see it
• ⌘K - search across plugins, projects and machines from anywhere

Click a row to open the detail panel: versions per machine, formats, size, validation state, and the licence linked to it where one is known.

What the studio owns, what it costs, and where it runs. Studios hold perpetual licences almost exclusively, so the page leads with what is owned rather than with renewals.

The three figures at the top:

• licenses - the total, split into perpetual and subscription
• invested - money, in the currency it was recorded in. Mixed currencies are never added together: the largest is shown and the rest named beside it, because a sum across currencies is an amount in none of them
• idle - licences on no machine at all, and what they cost. This is the number that turns into a decision: sell, transfer, or reinstall

Statistics (next to the figures) opens three panels:

• Data confidence - how many licences have a price recorded, and where each seat allowance comes from. Every other number on the page is only as good as this one
• Activation - how many licences depend on iLok, an online account, a serial, a dongle. This is what tells you what stops working if a dongle is lost or an account is locked
• Invested by vendor - per currency, one-time money and yearly money kept apart. Click a vendor to filter the table to it

Filter chips:

• Expired, installed - lapsed licences still sitting on machines. These break in the middle of a session, which is why they come first
• Over seats - running on more machines than the licence allows, where the allowance is actually known
• Check seat terms - on more than one machine with no stated allowance. Not a breach: a prompt to look it up (see below)
• Idle - installed nowhere
• 30d / 60d / 90d - renewal horizons. They appear only if some licence has an expiry date at all

The table shows the licence, Machines ("2 of 3" with a tick per machine, and where the allowance came from), Expires as a distance rather than a date, and Paid - one-time, per year, or Free.

Open a row for the rest: which machines have it and when each was last seen, the seat allowance with the vendor's own wording and a link to where it was read, what was paid and when that was recorded, and how the licence activates (method, iLok ID, linked plugin).

Bundles is a separate tab with its own totals.

"2 of 3 machines" needs a number to compare against, and that number can come from three different places. The dashboard always says which, because the three are not equally certain:

1. What you recorded. If the organization recorded a seat count for the licence, that wins over everything else.
2. Free or unlimited. A plugin the vendor gives away, or licenses without a seat limit, has no allowance to exceed - the row says so instead of counting.
3. The vendor's published terms. Read from the plugin catalogue's licence-terms scan. The row shows the vendor's own sentence and links to where it was read. Where the answer was taken from another plugin by the same maker rather than read for this one, it is marked inferred - it is a reasonable guess, not a reading.
4. One machine, assumed. When nobody has stated an allowance, one machine is assumed, because that is what a paid perpetual licence most often covers.

Only a stated allowance can be exceeded, so only those land in Over seats. An assumed one on several machines lands in Check seat terms instead - many perpetual licences allow two or three activations, and calling that a breach would be an accusation on a guess.

Every DAW project the agents found, and the one question a studio asks about a session: will it open on that machine?

The line under the title counts the projects and DAWs, and names the two things worth acting on: projects that won't open somewhere, and projects with missing audio.

• Won't open somewhere - a required plugin is missing on at least one machine that has the project
• Licence issue - it opens, but a machine cannot authorise one of its plugins
• Missing audio - the project references audio files the scan could not find
• DAW and machine selects, search, and Export CSV

Picking a machine re-scopes the table to that machine alone: the column becomes On <machine> and answers for it - opens, so many plugins missing, or a licence issue.

Columns: the project with its DAW, key, tempo and sample rate; Opens on (how many of the machines that hold it can open it); Needs (required plugins, and how many are missing); Audio; and Last opened.

Open a row for the plugins the project uses - problems first, the installed ones behind a toggle - then each machine's verdict, the missing audio paths, and where the project file lives.

Sample libraries across the fleet - the Kontakt and Spitfire-sized installs that decide whether a session can be opened in another room.

• Vendors down the left, largest storage first, with the count and size for each. The order does not change as you filter, so a vendor never moves while you reach for it
• Type chips - orchestral, synth, drums and the rest, each with its count
• Not on every machine - the libraries that are missing from at least one machine
• Machines column - "2 / 3" with a tick per machine

Open a row to see which machines have it, where it is installed on each, how big it is there and when it was last seen - and which machines are missing it. A copy noticeably smaller than the largest one is flagged as a possible partial install, which is what a missing mic position or content pack usually looks like.

Samples browses the fleet's sample files as a folder tree. Pick a folder on the left and the files appear on the right with format, sample rate, channels, length, the machine holding them and their category tag. Tag chips at the top narrow the list to kicks, snares, loops and so on.

Presets lists the custom presets the agents found, grouped by the plugin they belong to.

Which DAWs are installed where, and at which version. The map view is the DAW × machine grid; the table lists each host with the machines that have it. A DAW with a newer version available is marked, the same way plugins are.

Equipment - audio interfaces and hardware the agents detected - is listed under the machine it belongs to, from Machines.

The same question - is this on every machine that needs it? - is answered in the place where you would ask it, rather than in one separate screen:

• Plugins → Map - the plugin × machine grid, with the version in each cell. A plugin can reasonably be expected on every machine, which is what makes the grid worth reading
• DAW → Map - the same for DAW hosts
• Licenses → Machines - how many machines run each licence, against what it allows
• Libraries → Machines - how many machines have each library, and which are missing it
• Projects → Opens on - how many of the machines holding a project can actually open it

Every machine enrolled in your organization:

• Status dot - green while the machine is reporting, grey once it goes quiet
• Name - as set during agent setup
• Sample rate and Interface - the audio device in use
• User - the account last signed in on that machine

Open a machine for what it holds: plugins, projects, presets, libraries and equipment, each scoped to that machine.

Reports → Exports generates a file from your fleet data. Pick what to export and the format:

• Fleet Overview, Plugin Inventory, License Summary, Library Inventory and DAW Inventory
• as CSV, XLSX, PDF or JSON

Generated exports are listed underneath, so a file can be downloaded again without rebuilding it.

Commands you can send to a connected machine from the browser:

• Rescan - a full plugin rescan on the target machine
• Sync Now - an immediate sync of what it already knows
• Restart Agent - restarts the background service

Each command is tracked from pending through delivered to succeeded or failed, and the history stays on the Actions page. A command for a machine that is offline waits until it comes back.

Invite team members to your organization so they can view and manage the fleet:

1. Go to Settings → Team.
2. Click Invite Member and enter their email address.
3. Choose a role: Admin (full access), Member (view + manage), or Viewer (read-only).
4. They receive an email invitation. Once accepted, they appear in the team list.

API keys connect your desktop agents to the cloud. Manage them in Settings → API Keys:

1. Click Generate Key.
2. Give it a descriptive name (e.g. "Studio A - Mac Pro" or "Laptop - Windows").
3. Copy the key immediately - it won't be shown again.
4. Paste it into the desktop agent (Account → Cloud).

• Revoke: click the trash icon on any key to immediately disconnect that workstation.
• Key limit: your plan determines how many API keys you can create.
• Last used: each key shows when it was last used for a sync.

• General: organization name, timezone, notification preferences
• Team: invite/remove members, change roles
• API Keys: generate, copy, revoke workstation keys
• Plan & Billing: upgrade/downgrade plan, view invoices, update payment method
• Sign out: log out of the Web Dashboard

The bell in the header shows the newest open alerts; the Alertspage shows all of them, filtered by status (active, snoozed, resolved) and by severity. What raises one:

• License expiring - inside the warning window
• License expired - past its expiry date
• License seat overage - in use on more machines than the licence allows
• Plugin crashed - a plugin failed validation on a machine
• Plugin policy - a version your policy flags, and separately when a blocked version is actually installed somewhere
• Project missing required plugins - a project needs a plugin no machine has
• Workstation offline - a machine has stopped reporting
• Agent command failed - a remote command did not complete

Snoozing an alert keeps it out of the way without closing it; it returns when the snooze runs out, if the cause is still there.