Change and save in one place
Per-section save: Each section usually has its own Save (or Apply) action. Change options in the panel and click Save. The request is sent to the FleekDash backend (e.g. REST API); success toast or message confirms. Unsaved changes may be lost if you switch section without saving (depending on implementation).
Validation: Required fields or invalid values may block save and show inline or toast errors. Fix the values and save again.
Persistence: Saved settings are stored by the backend (WordPress options or FleekDash API). They persist across sessions. Refreshing the page or reopening the section loads the saved values.
License: License Activation has its own flow: enter key → Activate; Deactivate or Refresh to update status. License state is used for plan and feature access across FleekDash.
Change and save in one place; no hunting for "where did I save that?"
<!-- seo-geo: content-enrichment -->
In practice
Settings Center — per-section save, validation, persistence, license flow. On this page, Change and save in one place is covered in detail: what it looks like in the admin, the exact controls it exposes, and how it behaves when you use it day to day. Because change and save in one place is part of Settings Center — grouped options and instant persistence for all FleekDash configuration — the settings you touch here interact with the rest of the feature; when in doubt, open the feature overview and follow the docs in order.
What persists where
Most settings persist to the WordPress database the moment you change them — there is no draft state for site-level options. Visual preferences that belong to you rather than the site (sidebar width, panel docking, density) are stored per device in local storage, so they follow you between sessions but not between browsers.
If a change does not survive a refresh, check whether it is a device-level preference first — that is expected behavior, not a lost setting.
See also
Need a hand? Contact support or head back to the Settings Center guide.