Disabling a module does not delete anything. To permanently remove content — for example, all your old event posts — delete the content inside that module first, then disable the module if needed.

Modules operate at the feature level, not the individual-page level. To hide one specific page, unpublish it from within the relevant admin section.

Modules are a site-wide switch, not a per-user permissions control. To restrict what a team member can access, manage user roles separately.

Disabling a module removes the route entirely. For targeted traffic control — blocking specific IPs or user agents — use the Blacklist module instead.

Image Studio is gated by plan. For all other billing questions, contact SGEN support rather than adjusting module toggles.

The toggle for each changed module reflects its new state on the Modules page.

Modules you disabled no longer appear in the left sidebar. Modules you enabled appear in the sidebar and their routes are live.

Front-end routes for disabled modules return a not-found response. Routes for newly enabled modules go live.

Posts, records, and settings for disabled modules are stored and reappear when you re-enable the module.

Check that your browser is connected to the internet. Reload the page, re-apply your toggle changes, and try saving again.

Image Studio is locked to the Enterprise plan. Its control shows an Upgrade prompt instead of a standard toggle. All other modules should toggle freely. If a different module appears grayed out, contact support to confirm your plan includes it.

Try a hard reload — Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac. Browser caches sometimes show a stale version of the sidebar. If the item persists after a hard reload, contact support.

Disabling and re-enabling preserves data in the database. Appearance settings for a module's front end are separate from the module toggle itself. Confirm the content records are intact, then check display settings within the module.

Re-enable the module from the Modules page and click Save Changes. After saving, the module's admin pages reappear in the sidebar. No content was deleted.

The left sidebar reflects exactly which modules are currently enabled. Disabling a module removes its entry from the sidebar. Re-enabling it restores the entry.

If you injected a third-party script that targets a module's front-end output, disabling that module will break the script's target. Review your Custom Codes before disabling a module with active script dependencies.

When you disable a module, its front-end routes become inactive. Visitors who arrive at those old URLs will see a not-found page. To handle incoming links gracefully, add a redirect rule before you disable the module.

The SEO Manager is itself a module. Disabling it removes the bulk SEO dashboard but does not affect the individual page SEO fields built into the page editor.

This is the one module gated by plan. All other modules are included in your current plan and can be toggled at any time.

You need admin-level access to your SG PANEL site to reach the Modules Config page.

The list is long — knowing the module name or its category saves time. Use the category filter chips to narrow the list quickly.

If you are disabling a module with active front-end routes — for example, Events or Redirects — let your team know before you save. The change takes effect immediately when you click Save Changes.

Core system modules are always on and do not appear as toggleable items on this page.

No. The Modules page states directly: "data is preserved and reappears when you turn it back on." Disabling a module hides admin pages and deactivates front-end routes. It does not remove records, posts, or settings.

Yes. Toggle as many modules as you need in a single session. None of the changes take effect until you click Save Changes.

Enable all stages every toggleable module to on. Disable all stages every toggleable module to off. In both cases, nothing changes until you click Save Changes.

Image Studio requires the Enterprise plan. Its control shows an Upgrade prompt rather than a standard toggle. All other modules are included in your current plan.

Front-end routes for the disabled module become inactive. Visitors who arrive at those URLs will see a not-found response. To send them to a useful page instead, add a redirect rule in the Redirects module before you disable.