neuro-frontend · v4.0.0-dev · commit 276788ca6

Every feature of the shopping-centre back office, traced through the routes, controllers, models, abilities and the translation file: what it does, who can reach it, how it succeeds, and every way it is known to fail.

FeaturesAreasUse casesHappy pathsFailure pathsFindings
921033113643632 (2 high · 14 medium)

Product areas

AreaFeaturesFailure pathsFindingsWhat it covers
Platform & Access11347Authentication, session lifecycle, centre scoping and the landing desktop — the shell every other feature runs inside.
CRM241019Customer, segment, store and receipt management: the customer database and everything that reads or writes it.
Marketing10607Activities (campaigns with loyalty mechanics), email campaigns and the embedded loyalty/gift/booking platforms.
CMS7555Content published to the mobile app and web: proposals, push notifications, categories and the app button layout.
Intranet10624Centre-to-tenant operations: sales declaration and closing, annual statements, communications, documents, footfall, SAFT-E and utilities.
Analytics38—Dashboards and the prebuilt CRM / data-quality panels.
Play Center16—Supervised play-area stays: child check-in and check-out against capacity.
Configuration16667Tenant and platform administration: centres and their modules, staff accounts, reference data, dashboards and operational tooling.
Smart Assistant13—The embedded conversational assistant (CandelarIA).
Cross-cutting9418Shared engines and layers reused by many features: imports, exports, filters, files, i18n, realtime, permissions and error handling.

The map

Start here

Browse

Generated 2026-10-12 by doc/tools/build-feature-atlas.py from doc/feature-inventory.json. Edit the JSON and re-run; do not hand-edit generated notes.