This device isn’t Warranted yet. Its key (non-extractable, never leaves this browser):
Scan this with the Genesis app — “Warrant a console login” → Scan device-pub QR.
Warrant with your shares — drop 3 share files here (or click to pick). Combined and signed in this browser only. Shares are never uploaded, never logged, wiped after signing.
OR
On the key device: genesis-cli warrant root.key <device-pub-hex> — then paste the warrant signature:
ARGUSNOC for Meraki — Operationally Driven, Network Operations Centerread-only
Environment comparison
Live config audit of every registered environment — triggers, automations, macros, views, brands, groups, forms, hours — run against each tenant and compared. Same counts across the row = same configuration. The triggers & automations rows are what actually send a guest email.
…
◫ Environment diff — Production → Sandbox
Object-level diff per category. Prod-only = missing in sandbox · Different = same name, different definition · Sandbox-only · Same. Refresh copies prod’s definition into the sandbox (sandbox is the only write target).
…
⚙ Argus settings · synced across your machines
🔑 Crew — who can sign in
Applies toSign-in (Google)
The allow-list behind member sign-in, enforced server-side at every login. Add a person’s exact email or a whole @domain, then send them argus.com.ai/app — they sign in with Google immediately. Login proves who; this list decides what. A removal applies at their next sign-in.
Lab Features & write controls
Applies toOperationsNetworkSecurity Audit
New / write-capable features start in Lab Testing — live only on lab/test locations. Enable for Production to roll out everywhere; after 7 days it’s archived (shipped).
Lab/Test keywords — a location qualifies only if its name contains one of these as a whole word. Comma-separated:
⏻ Allowed networks WRITE
Applies toevery feature in Production
The one list of real networks Argus may write to. Every feature in Production (Set VLAN, Set PoE, Bind Template, Action Plans) inherits this list; a feature can optionally narrow itself to a subset in its own card. Everything else is write-blocked, enforced here and server-side. Lab/test-named networks stay writable in Lab without being listed.
Op-targets K
Applies toOperations
The Operations tab is a stack of op-targets — each a named group of devices we watch at a store. Two kinds: VLAN (everything connected on given VLAN(s), e.g. Toast POS) and Roster (named devices at fixed IPs we expect live + on a set VLAN, e.g. Konductor). Reorder, retitle, edit, add — or archive / request delete (no hard delete; request delete signals Joey to remove it for good).
Planned-missing devices
Applies toOperations
Set inline & per-network — in a roster op-target’s table click mark planned on any missing device. Accepted devices show PLANNED not MISSING and don’t break SOLID (that store only).
📡 API endpoint
Applies toOperationsNetworkSecurity Audit
Every Argus REST call goes to this bridge — a read-only proxy. The org API key lives only on the bridge, never in your browser.
REST endpoint:…
Upstream:Meraki Dashboard API v1 — https://api.meraki.com/api/v1
Joey Castillo