SAVHN Module Marketplace: Frequently Asked Questions
SAVHN's modules aren't locked together into one fixed bundle. Each one — CRM, HRMS, Payroll, Finance, Projects, Tickets, Timeline, Meetings, Chat, Documents, Client Portal, Reports, Learning, Skills, Automations, and more — can be individually enabled or disabled for your organization through the Module Marketplace, right from your admin area. This FAQ covers how that actually works: dependencies between modules, what happens to data when a module is turned off, how visibility is controlled once a module is on, and the practical questions that come up as you adjust your module footprint over time.
Enabling & Disabling Modules
Where do I turn modules on and off?
The Module Marketplace lives in your organization's admin area. It shows every module available to your organization — grouped by core platform modules and any Industry Cloud modules — with a clear enabled/disabled state for each, and a simple toggle to change it, subject to your licensing. The Marketplace page also shows a running total, like "X of Y optional modules enabled," so you can see your footprint at a glance without clicking into every individual card.
Are some modules always enabled and can't be turned off?
Yes — certain foundational capabilities are marked as always-enabled because the platform depends on them functioning (for example, core account and organization settings). The Marketplace clearly distinguishes these from optional modules you can freely toggle, so you always know which parts of your configuration are foundational versus which are genuinely your choice to make.
What does "X of Y optional modules enabled" mean on the Marketplace page?
It's a running count that tells you, out of all the optional modules your organization is licensed for or could add, how many are currently switched on. It's a quick way to see your actual footprint on the platform at a glance rather than digging through a long list module by module, especially useful for an admin auditing what's actually in use versus what was enabled once and forgotten.
Can I enable a module during my trial?
Yes. During the 7-day free trial you can enable and try the modules you're evaluating in a real organization workspace, the same Marketplace mechanism you'd use after converting to a paid license. There's no separate, more limited trial version of the Marketplace — it's the identical interface and behavior.
Is enabling a module instant, or does it require setup time?
Enabling a module through the Marketplace makes it immediately available in your navigation — there's no waiting period or provisioning delay. What may take additional time afterward is configuring the module to your specifics (custom fields, role visibility, integration connections), but the module itself is usable right away once toggled on.
Dependencies
Do modules depend on each other?
Some do. A module can have a defined "depends on" relationship with another module — for instance, a module that surfaces project financials might depend on Finance being enabled to have anything meaningful to show. The Marketplace surfaces these relationships directly on each module's card, so you're not left guessing why a module isn't fully functional after you enable it.
What happens if I try to enable a module without its dependency?
The Marketplace shows you the dependency status directly — each module lists what it depends on and whether that dependency is currently enabled, using a clear visual indicator (typically a badge showing whether the dependency is satisfied). This is meant to prevent the confusing situation where a module is technically "on" but can't actually do anything useful because a module it relies on isn't, which would otherwise look like a bug rather than a missing prerequisite.
What does "required by" mean on a module's card?
It's the reverse view of dependencies — which other enabled modules in your organization rely on this one. If you're considering disabling a module, checking what currently depends on it tells you what else might lose functionality as a result, before you make the change rather than after something else breaks unexpectedly.
If I disable a module other modules depend on, does everything break?
The Marketplace is designed to surface this risk to you clearly beforehand — showing which enabled modules require the one you're about to disable — so you can make an informed decision rather than discovering broken functionality after the fact. It's on you as the admin to review that information before confirming the change, but the information itself is presented rather than hidden.
Data & Configuration
What happens to my data when I disable a module?
Disabling a module removes it from your organization's navigation and stops new activity in it, but it does not delete the historical data that already exists inside it. If you re-enable the module later, your prior records are still there. Module licensing is meant to reflect what you're actively using right now, not force you into a destructive choice every time you want to pause something, for example during a seasonal lull or while re-evaluating whether a module fits your workflow.
If I disable a module, can other modules still reference its data?
This depends on the specific relationship between modules — a dependent module that relies on the disabled one for active functionality may lose access to that functionality while the dependency is off, which is exactly why the Marketplace surfaces dependency and "required by" relationships up front, before you toggle anything off, so you can weigh that trade-off deliberately.
Can I control which employees see a module, separate from whether it's enabled for the organization?
Yes. Enabling a module for the organization is one layer; per-role visibility is a separate layer on top of it. An admin can restrict a role to a subset of the organization's enabled modules — for example, keeping Payroll and Finance visible only to Finance and HR roles even though other modules are broadly visible to everyone. A role with no explicit restriction sees every module the organization has enabled, so setting up role-based visibility is a deliberate configuration step you take as part of rolling a new module out to your team.
Does adding a module change my billing immediately?
Enabling a module you're licensed for through the Marketplace reflects your configuration; the commercial side of adding a new module to your license is handled through the same pricing mechanism as your original setup — the Visual Pricing Configurator or your account team — rather than being an invisible automatic charge that appears on your next invoice without warning.
Can I see what an Industry Cloud actually includes before enabling it?
Yes — Industry Cloud modules are grouped and labeled distinctly in the Marketplace (as industry modules, separate from core platform modules), so you can see exactly which underlying modules make up a given Industry Cloud package rather than treating it as an opaque bundle you're taking on faith.
Who can enable or disable modules for the organization?
This is an admin-level action within your organization — it's part of the same admin area that controls role permissions and other organization-wide settings, so it isn't something a general employee role can casually toggle on their own.
If I disable a module by mistake, is it easy to undo?
Because disabling doesn't delete data, re-enabling a module you turned off by mistake restores it to the same state it was in — your records, configuration, and history are all intact, so an accidental toggle isn't a destructive event you need to be especially cautious about, beyond re-checking any dependent modules that may have been temporarily affected.
Does the Marketplace show modules I'm not currently licensed for, or only ones I've already paid for?
The Marketplace is generally where you discover the full set of modules available to explore and enable, not just a narrow list of what you've already committed to — part of its purpose is letting you see what else exists on the platform so you can decide whether to add it, with actual enablement subject to your licensing being confirmed through pricing.
Can I see a module's dependency chain more than one level deep — dependencies of dependencies?
The Marketplace surfaces the direct dependency relationships on each module's card — what it depends on, and what depends on it. For a module with a longer chain of relationships, tracing the full picture may mean checking a few related module cards in sequence, since each card shows its own direct relationships rather than an expanded multi-level tree on a single screen.
If two modules both depend on the same third module, does disabling that third module affect both?
Yes — dependency relationships aren't exclusive to a single dependent module. If Finance, for example, is a dependency for more than one other enabled module, disabling Finance would affect every module that lists it as a dependency, which is exactly the kind of situation the "required by" list on Finance's own card is meant to surface before you make the change.
Does the Marketplace distinguish between modules included in my Industry Cloud and ones I've added separately?
Industry Cloud modules are grouped and labeled distinctly from core platform modules in the Marketplace, which gives you visibility into which modules came from your Industry Cloud package versus which you've added on top of it independently, useful if you're trying to understand your actual footprint versus what came pre-configured.
Is there a way to preview what a module looks like before fully committing to enabling it for the whole organization?
The most direct way to evaluate a module before a full organization-wide rollout is through a trial organization or by enabling it during your 7-day free trial, where you can use it hands-on with real data before deciding whether to roll it out to your full live team.
If a module I want isn't in the Marketplace, what does that mean?
The Marketplace reflects modules that are actually built and available on the platform — if something isn't listed, it likely means it isn't a shipped module today rather than a display bug. If you're looking for a specific capability you don't see, /book-demo is the right place to ask whether it exists under a different name, is part of an Industry Cloud rather than a standalone module, or genuinely isn't built yet.
Does enabling a module through the Marketplace require a page reload or does it apply immediately?
Enabling a module updates your organization's configuration and the module becomes reachable through navigation without requiring you to contact support or wait for a manual provisioning step — it's a self-serve toggle, not a request queued for someone else to action.
Can I see a history of which modules were enabled or disabled and when?
Administrative actions like module enablement changes are the kind of event that fits within SAVHN's broader audit logging approach, which records real actor, action, and timestamp for platform actions — worth checking your organization's audit log if you need to trace when a specific module change was made and by whom.
Is the Module Marketplace the same interface for every organization, or does it look different depending on my Industry Cloud?
The Marketplace interface itself is consistent — the same enable/disable mechanics, dependency indicators, and role-visibility controls — regardless of which Industry Cloud or module combination your organization has. What differs is the specific list of modules shown as included in your Industry Cloud versus available to add, not the underlying interface or mechanics.
Want to see the Module Marketplace and its dependency handling for yourself? Start a 7-day free trial — no card required — and try enabling and disabling modules in a real organization workspace. To plan out a specific module combination in advance, use the Visual Pricing Configurator, or reach out to the developer team with questions about dependencies for your setup.