Setup in progress
Your account has access, but setup is not complete yet. An administrator can finish setup and let you know when AXWEL is ready.
Workspace access
Ask an administrator to grant access to a workspace, then try again.
What needs attention across the store right now.
One inbox for shoplifting, urgent interactions, after-hours AI review, and operations issues.
Live Telnyx voice (2026-08-11) and SMS (2026-08-19, from +18887540480) canaries passed on the Railway origin under notify_only. Paging, siren, and autonomous dispatch are not yet proven end to end. Do not rely on AXWEL as your only alarm or life-safety notification channel. Keep your existing monitoring or dispatch arrangement in place.
Alarm response, dispatch readiness, incident review, and escalation in one security workspace.
Contacts and escalation configured here can receive live Telnyx SMS and voice under notify_only (voice canary 2026-08-11; SMS canary 2026-08-19 from +18887540480). Paging, siren, and autonomous dispatch remain unproven — keep an independent alarm or monitoring channel in place.
Camera sites you already added appear here automatically. Arm, disarm, tune thresholds, and manage schedules.
Recent state changes, PIN attempts, dispatch actions, and resets.
Unreviewed AXWEL Guard incidents for alarm-response operations.
Journeys from entry to exit, buying or lost.
Visitor review queue, post-exit checks, and journey replay context.
POS import status, recent sales, data quality, and linked camera clips.
MightyCall sync, transcripts, retail sentiment review, and recording playback. First sync backfills the last 72 hours. This list defaults to today’s calls — choose Yesterday or Custom to change the range. The top-bar time window does not apply here.
Coaching exceptions, scores, and flagged interactions.
Faces seen at the register during a completed sale. Confirm a name to label them employee:Name and exclude them from doorway visitor counts. Dismiss leaves them as visitors.
Issue a clip-backed notice, email the employee, and keep open/click confirmation.
Live view, recording state, zones, clips, and camera controls.
notify_only. They do not enable autonomous dispatch or replace an independent life-safety channel.
Unified camera feature states, recording hours, people-only storage, audio review, VAD, theft detection, codecs, and no-audio flags.
Draw a box on the camera, then enable only the monitoring checks that matter there. Visitor journeys can start at an entry zone or by person identification.
Review footage, status, person detections, and storage impact.
At-a-glance operational summary — incidents, spend, clip-export backlog, and queue backlog.
What your team has taught this store's AXWEL — corrections, reviews, docs, and flags — and how it's tuned as a result. The more you use it, the more it fits this store.
Set up custom watches for people, doors, objects, facility state, cameras, and event sources.
Describe the condition, where it applies, and how long it must persist before AXWEL alerts your team.
Practical monitor templates matched to AXWEL's current camera, event, journey, and ops-inspection abilities.
Confirmed watches and their current duration/evaluation state.
Semantic search across incidents, transcripts, reviews, ops issues, and AI artifacts. Reranked when a reranker is configured.
This account must be opted into AXWEL's Fireworks spend share before scene understanding and other cloud AI features can run. This is separate from your fireworks.ai billing balance.
Internal AI spend reconciled against Fireworks billing. Each refresh queries a billing API, so it runs only when you click Refresh.
Ask the operations copilot. Each answer runs a cloud model and may call tools, so it fires only when you send.
Scheduled ops-inspection status, recent runs, and unresolved issues.
Persisted briefings, packets, runbooks, and audit answers.
Setup, diagnostics, integrations, storage, and installer tools.
Account members, pending invites, and workspace permissions.
AI intelligence, timezone, storage, backups, and remote NAS setup.
Tenant-scoped security history, including platform impersonation start and revoke events.
Worker health, queues, model usage, and periodic task status.
Enrolled edge devices, health, tokens, OTA update state, and device telemetry. Store locations without an installed agent stay on Integrations.
Link a Nest Google account, discover cameras, enable WEB_RTC or RTSP streams via go2rtc, and optionally backfill Nest Aware history.
A location is the site a camera belongs to (one per store or entrance), not the Nest camera's Google name. Add one here, then pick it in the Location dropdown on a camera below and click Save location. Use Save name on a location row to rename the site — that does not change the Location ID or the camera name. Installing an edge agent is separate — use Admin → Agents when you have a device to enroll.
Sign-in uses Google Device Access (Sandbox is enough; “Apply for commercial development” is optional). Cameras must be migrated to the Google Home app. Battery cameras stream over WEB_RTC and the older wired line over RTSP; go2rtc restreams either.
32c4c2bc-fe0d-461b-b51c-f3885afff2f0 — not your Google Cloud project ID)./ if present). For the simplest flow you can use https://www.google.com in both places./partnerconnections/<uuid>/auth).?code=... in the address bar. Paste either the bare code value or the whole redirect URL into Authorization code (codes are single-use — get a fresh one if exchange fails).Nest Aware history has no API. Use this only when you need recent clips imported onto the AXWEL timeline:
Add a camera from the Cameras page to get a unique username and show-once password. Point the camera at the host and port shown here, use PASV, prefer FTPS, and date folders YYYY-MM-DD.
System-admin custody controls for orphaned or decommissioned edge devices.
Policy coverage, regulated feature blocks, derived artifact inventory, and erasure status.