ContentMetrc & Compliance

Metrc Basics: Navigation, Permissions, and Search

How Metrc's menus, facility switching, search filters, and templates actually work, and the settings most people never find.

BT

BulkMarket Team

BulkMarket

July 2, 20264 min read

Metrc looks like any other business web application: a top navigation bar, drop-down menus, grids of data you can sort and filter. What's not obvious until you're in it is how much of what you see depends on your license type and your specific permissions, not just what button you clicked.

The Menu You See Isn't the Menu Everyone Sees

A menu only appears in your navigation bar if you have permission for at least one option under it. Two employees at the same facility can look at completely different toolbars depending on what the Account Manager granted them.

License type narrows things further, before permissions even come into play. A Cultivator gets Plants, Packages, Transfers, Admin, and Reports. A Retailer swaps Plants for Sales. A Distributor gets a Transfers Hub that a Cultivator never sees. A Testing Laboratory gets a Test Product function nobody else has access to. The menu structure isn't generic software chrome, it's shaped around what your specific license is legally allowed to do.

One function, the Friendly Name, is locked to the Account Manager only, on every facility type. It lets you shorten your business name for display inside Metrc, and it's the one setting employees can't touch regardless of their permissions.

Running Multiple Licenses

If you're credentialed on more than one facility, a drop-down in the upper right lets you switch between them. Employees tied to a single license never see this option; it only shows up once you actually have more than one facility to choose from. Everything you do in Metrc happens inside whichever facility is currently selected, so double-check which one you're in before making entries, especially if you're managing licenses across different properties.

Reading the Signals

Metrc uses color to flag status at a glance. Green text means something resolved cleanly, a transfer that completed successfully, for example. Red means it needs attention, most commonly a package placed on administrative hold by the state. Two notification systems back this up: a banner across the top of the page for urgent, account-wide issues, and an envelope icon that holds specific notifications like transfer rejections or package adjustments made by someone else in the chain. Check the envelope regularly. It's where you'll first learn a transfer got kicked back.

Search Is More Capable Than It Looks

Every grid in Metrc can be sorted by clicking a column header, and filtered through the Column Settings menu. The filter logic supports contains, does not contain, starts with, ends with, equal to, and not equal to, plus greater/less than comparisons for quantity fields, and you can stack two conditions with an and/or.

The practical version of this: if you only remember the last three digits of a package tag, search ends with or contains instead of trying to recall the full UID. If you know the first three and last two digits, combine a starts with and an equal to filter with and. If you're pulling every transfer from a specific month, filter the month and year together. These aren't edge cases, they're how you'll actually find things once your tag inventory gets into the thousands.

One setting worth knowing: column layout changes persist across sessions in the same browser, but not across different browsers or devices, unless you check "Save grid configurations remotely" on your User Profile. If you work from more than one computer, turn that on once and stop rebuilding your view every time you switch machines.

Templates for Repeat Work

When you're taking the same action on multiple plants or packages at once, harvesting several flowering plants, or creating several new packages in one pass, Metrc activates a template. Enter a value once in the template and apply it across every row, instead of retyping it for each one. It's not universal: fields like plant weight or package quantity are inherently different per item and still have to be entered individually. But anything that's genuinely the same across the batch, a harvest name, a shared date, doesn't need to be typed twice.