Zones (Admin)

Executive summary

Zones is an optional registry screen under /dashboard/zones for legacy or operational data. The current Nest admin JWT does not carry zone_id for scoping—admin access is driven by modules and explicit store_id / tenancy rules in services (see Admin panel overview and Tenancy — stores and outlets).

---

Goals and non-goals

Goals	Non-goals
Model org/geographic splits for RBAC	Replace DNS or network zoning
Link zones to stores/vendors	Detail regional tax law

---

Current platform behavior

• List/create/detail/edit routes under /dashboard/zones (see table).
• See Tenancy — stores and outlets for data flow.

---

Sequence: happy path

1. Master admin maintains zone registry.
2. Assign admins to zones via staff/role processes.
3. Zone-scoped users operate stores/vendors inside zone only.

---

Security and operations

• Changing zone boundaries is high impact—coordinate with data team and audit trails.

---

Test scenarios (UAT / QA)

ID	Scenario	Expected
Z1	List zones	CRUD per permissions
Z2	Non–Master admin	Sees zones only when APIs allow
Z3	Unauthorized access attempt	403 / empty

---

Routes

Path	Purpose
/dashboard/zones	Zone list
/dashboard/zones/create	Create zone
/dashboard/zones/:id	Zone detail
/dashboard/zones/:id/edit	Edit zone

What a zone is

A zone is an organizational label in the legacy MySQL model (for example zones rows linked from stores.zone_id where present). The Nest admin JWT does not use zone_id for authorization—use modules and explicit store_id / service checks instead.

See Tenancy — stores and outlets for API behavior and Admin panel overview for modules and Master admin.

List

• Search — debounced (400ms), 10 rows per page.
• Actions — view (/dashboard/zones/:id), edit, delete (with i18n confirmation).
• Delete — calls deleteAdminZone and refreshes the list.

Related

• Managers (Admin) — staff accounts and roles.
• Modules (Admin) — non–Master admins and module keys (see that page).