Map setting (UI preview)
Provider configuration and module mapping screens — layout only; data is not persisted to tenant APIs in the current console build.
Navigation: /dashboard/setting/general-settings/map-setting
Production status
The Map Setting experience is implemented with local in-memory lists and static seed data in the current console. Add, edit, delete, and module mapping changes do not call tenant configuration APIs in this build. Treat this page as a UI preview only — do not document it as a guaranteed production integration.
What you see
- Provider Configuration tab — grid of provider cards (name, icon) with edit and delete affordances.
- Module Mapping tab — assigns a provider to modules such as trip, geofence, or live tracker (defaults are illustrative).
Add Provider opens a modal to pick a provider type and display name; saves update browser state only.
Permissions and access
Route guards may still apply. If you cannot open the page, see Permissions. Dedicated CanI codes for each map action are not consistently wired in the preview implementation.
Troubleshooting
- Changes disappear after refresh: Expected for preview data; nothing is persisted server-side in this mode.
- Expecting production map keys: Configure real keys only when your deployment exposes a backend-connected map settings flow; this preview does not replace that.
Related
- Overview
- AI settings — similar preview pattern for AI providers.