Business owners
Useful for setting the visual identity of the business, choosing what customers and staff will see, and keeping the platform aligned with the venue brand.
Noesia Smart Waiter / Module Documentation
Free Event-Driven IoC Isolated/X-Core Micro-Frontend Platform Control Surface
SETTINGS
Settings is the central control surface of Noesia Smart Waiter. It is where the business defines identity, visual behavior, feature emphasis, and key runtime preferences for the whole platform. From shop name, logo, labels, icons, and sound behavior to weather and news language context, color logic, menu visibility, and general shell behavior, this module shapes how the entire installation feels and operates.
Who is it for
Built for the people who define how the platform behaves
Administrators
Useful for controlling labels, icons, weather and news behavior, sound, menu visibility, and the larger shell experience of the plugin.
Launch and maintenance teams
Useful during first setup, design refreshes, content corrections, or any time the installation needs to be tuned without touching deeper code.
Main Features
What Settings controls across the platform
Business identity and branding
- Shop or business name.
- Business logo and profile-style identity details.
- Core contact and business presentation details used by the platform.
Labels and action wording
- Edit the visible texts used in the Smart Waiter experience.
- Control action naming for the client-facing flow.
- Restore defaults when the installation needs to return to a known baseline.
Icons and visual defaults
- Control icons used by live customer actions.
- Keep the public interface aligned with the business style.
- Reset icon defaults when needed.
Sound behavior
- Enable or disable operational sound alerts where supported.
- Useful for venues that want an audible signal for live activity.
- Supports quieter or more active service environments.
Weather and news context
- Settings influence weather-related behavior and display context.
- News language or dashboard language choices affect how several dashboard-driven surfaces feel.
- Useful for installations that want localized operational context.
Dashboard language and pulse logic
- The chosen language context can influence Weather, News, SMART AI ALERT, and Global Pulse presentation.
- Useful for consistent tone across the dashboard shell.
- Helps the whole front surface feel unified.
Color system and visual feel
- Color variables shape the public and admin feeling of the experience.
- Useful for tuning the installation to a stronger brand identity.
- Works together with the wider visual system of the shell.
Menu Visibility Manager
- Control which navigation items and module entry points stay visible.
- Useful when the business wants a cleaner shell or only selected tools exposed.
- Helps tailor the installation to the exact role and venue needs.
How to Access It
Where the Settings module lives
Admin path: open the Noesia Smart Waiter admin area and select Settings from the plugin shell navigation.
Tier: this module is part of the Free tier.
Role expectation: intended mainly for administrators, owners, and managers who control how the platform looks and behaves.
Setup / Configuration
Recommended order for a clean first-time setup
Set the business identity first
Start with business name, logo, and the main identity details so the rest of the platform feels branded from the first moment.
Adjust labels, icons, and action wording
Shape the customer-facing action surface so it matches the language and personality of the venue.
Choose language and context behavior
Set the dashboard or news language context so weather, news, pulse-style surfaces, and related output stay consistent.
Tune sound, color, and navigation visibility
Finish with sound alerts, visual color behavior, and Menu Visibility Manager decisions so the shell reflects the real operational needs of the venue.
How to Use It
Typical admin flow inside Settings
Open Settings first after installation
This is usually the first serious control surface the business should configure before expecting the rest of the ecosystem to feel finished.
Complete identity and visual basics
Save brand name, logo, and the action texts or icons that shape the customer-facing experience.
Set contextual behavior
Adjust language-related and content-related settings that influence News, Weather, SMART AI ALERT, and Global Pulse style.
Control what stays visible
Use Menu Visibility Manager and related shell settings so the plugin exposes only what the installation actually needs.
Return whenever the business evolves
Settings is not one-time-only. Use it whenever branding, wording, visibility, or context behavior changes later.
Screens / Interface Guide
The interface areas that matter most
Brand and identity area
This area matters because it defines how the plugin represents the business visually and structurally from the top down.
Labels and icon controls
This area matters because small text and icon choices shape the public Smart Waiter feel more than many users expect.
Language and context settings
This affects how dashboard-aware surfaces such as News, Weather, and pulse-style content feel across the installation.
Sound and visual behavior
This gives the business control over the emotional tone and operational intensity of the experience.
Menu Visibility Manager
This is one of the most practical areas because it lets the admin simplify the shell and expose only what matters.
Restore and baseline actions
Default restore paths matter because they let the admin recover from over-customization and return to a trusted state fast.
Common Workflows
Real examples of how teams use Settings
Owner brands the installation before launch
Set business name, logo, labels, icons, and colors so the customer-facing Smart Waiter flow looks like a real branded venue experience.
Admin tunes dashboard context language
Use language-related settings so Weather, News, SMART AI ALERT, and Global Pulse feel unified instead of mixed or inconsistent.
Manager cleans the shell with Menu Visibility Manager
Hide unused entry points and leave only the modules that the venue actually needs in daily operation.
Team restores safe defaults after too many edits
When labels, icons, or styling drift too far, use the default restore path to get back to a known working baseline.
Troubleshooting
Common problems, likely causes, and the first fix path
The platform still shows old labels or icons
Issue: the business updated wording or icons, but the front still feels outdated.
Why it happens: changes may not have been saved as expected, or the installation may still be serving cached output.
What to do: save again, refresh the relevant page, and retest the public-facing flow after clearing any local or site-level cache that might still be active.
The dashboard language feels inconsistent
Issue: Weather, News, or pulse-style content does not feel unified.
Why it happens: dashboard language or news-related context may not match the intended output path.
What to do: review the relevant language settings first, then reload the dashboard-aware modules.
The menu looks too crowded
Issue: the shell exposes more entry points than the venue actually needs.
Why it happens: Menu Visibility Manager has not been used to tailor the installation yet.
What to do: simplify the shell by hiding what the current business does not actively use.
The setup feels over-customized and hard to manage
Issue: too many edits made the platform harder to maintain.
Why it happens: the business kept changing labels, icons, or visual behavior without a clear baseline strategy.
What to do: restore defaults where appropriate, then reapply only the changes that truly improve the experience.
FAQ
Fast answers before opening support
Is Settings a free module?
Yes. It belongs to the free tier and acts as the central control surface of the platform.
Can I change the business name and logo here?
Yes. Settings is the main place for identity and branding control.
Can I change labels and icons from here?
Yes. This is one of the key roles of the module.
Can I restore default text and icons?
Yes. Default restore paths are important when the installation needs to return to a safe baseline.
Does Settings affect Dashboard and News?
Yes. Language and context choices here can influence dashboard-aware modules such as News, Weather, SMART AI ALERT, and Global Pulse.
Can I control sound alerts here?
Yes, where supported by the installation flow.
What is Menu Visibility Manager for?
It lets the admin simplify the shell and expose only the parts of the plugin that the business actually wants visible.
Can color settings matter that much?
Yes. Small visual decisions can strongly change how premium, calm, or intense the whole experience feels.
Should I configure Settings only once?
No. It is also the place you return to whenever the venue changes branding, language, visibility, or design emphasis.
Is Settings mostly technical?
No. It is technical only in the sense that it controls behavior, but its real value is business-facing clarity and control.
Why is this module so important?
Because the rest of the platform reflects many of the choices made here.
Does it belong at the core of the installation?
Yes. Settings is one of the most central control surfaces in the entire Matrix.
The Noesia Matrix
⚙️ THE NOESIA MATRIX: KERNEL FABRIC ARCHITECTURE
The Noesia Matrix is the shared architecture language and module fabric behind Noesia Smart Waiter. This module is not just a static page; it sits inside an isolate-first modular system designed for shell-driven navigation, clean section ownership, extensible widget zones, and future-safe expansion.
The architecture direction is intentionally high-control: modular ownership, isolated assets, lazy-ready behavior, clean settings flow, predictable prefixes, maintainable service boundaries, and enterprise-safe discipline around structure, security, and extensibility. Noesia transcends the definition of a standard WordPress plugin, operating as a robust platform built upon enterprise-grade Service-Oriented Design.
Here is how the core engine is designed to minimize bloat, maximize stability, and keep the experience consistently fast and responsive:
Event-Driven Inversion of Control (IoC): The platform follows an IoC pattern via a decoupled Event Bus. The central core acts as a “Logic-Less Host” (Blind / DUMMY Kernel). It does not tightly bind itself to module internals; modules announce their own presence, capabilities, and state through controlled registration flows.
The Micro-Frontend Paradigm (MFE): The UI is not a giant monolithic block. Each application behaves as an independent Micro-Frontend with its own dynamic assets, specialized logic, and UI contracts.
Strict Asset Isolation & Lazy-Loading: Resource usage stays disciplined. A module’s CSS, JavaScript, and data components are loaded only when the user reaches or interacts with that specific application surface.
Decoupled Registry Pattern: The dynamic discovery layer allows applications to be added or removed quickly without rewriting core logic. If one application encounters an issue, the architecture is designed to contain that impact instead of cascading it across the platform.
Enterprise-Grade Security & Stability: The platform is reinforced with strict input sanitization, dynamic registry routing, and defensive safety gates across the stack. The data layer and the user interface remain deliberately separated for maintainability and risk control.
The Result: A scalable hospitality and clinical operating system engineered to manage mission-critical workflows securely — from intimate cafés to high-traffic venues and sensitive medical environments.
Support
Support, escalation, and what to send first
Check first
- Confirm the plugin version.
- Confirm the module name is Settings.
- Check whether the issue affects identity, wording, visibility, language, or visual behavior.
- Review the troubleshooting section above.
Collect before opening a ticket
- One clear screenshot of the issue.
- The exact text of any visible error.
- Short steps to reproduce.
- Which setting was changed right before the issue appeared.
Open support only after the fast checks above
When you open a ticket, include one clean screenshot, the exact visible error text, short reproduction steps, and the last setting you changed before the issue appeared. That reduces back-and-forth and speeds up resolution.
Open Support