Admin-only tools live in the top-right toolbar. There's also a developer login bypass for running the app locally.

Feature access whitelists

The ⚙️ Settings button opens Feature Access, which manages three separate lists:

• Commercial PO tab: who can see and use the Commercial PO tab.
• Manual warehouse PO: who can cut a manual warehouse / will-call PO from the Residential region tabs (see 3a. Cutting a Manual Warehouse PO).
• Service PO tab: who can see and use the Service tab: its PO list, shared drafts, PO pages, and the form that cuts a class-3 PO against a customer's service project and adds its parts to the job's sales order (see 3b. Cutting a Service PO).

Feature Access: three independent lists (Commercial PO tab, Manual warehouse PO, Service PO tab); the admin shows as admin • always on each.

<aside> ⚠️

The three lists are independent on purpose — the commercial team, the warehouse managers and the service coordinators are different groups, so adding someone to one does not grant the others. Add a warehouse manager to Manual warehouse PO only, and a service coordinator to Service PO tab only.

</aside>

• Type an @gofreedompower.com email and ADD.
• The admin appears as admin · always and can't be removed.
• Remove a user to revoke their access.

<aside> 🚦

The Service PO list starts empty. Nobody outside the admin can use the Service tab until someone is added to it, so this is the first thing to do after the feature ships.

</aside>

Overriding the scope check

Before a residential PO is cut or updated, the tool checks that the Sales Order, the finalized BOM and the Sunrise design agree on modules, microinverters and batteries, and holds the project back if they don't (see 3. Generating Purchase Orders, Scope check before every PO). The normal fix is a change order in the proposal tool.

When a PO has to go out anyway, the admin (the same admin who manages the lists above) can push it through. Nobody else sees this option.

A held-back project. Only the admin sees the reason box and OVERRIDE AND RUN.

1. In the progress view, find the "Project … held back: scope mismatch" panel.
2. Type the Reason for overriding (required, up to 1,000 characters).
3. Click OVERRIDE AND RUN. A new job runs that one project in the same mode (new PO or UPDATE PO), and the log shows "Scope check overridden by …".