Skip to content

Show or Hide Modules

Nova Industries is a fictional electronics manufacturer and distributor. A service coordinator needs Support and Selling, but not Manufacturing. An administrator finds an older instruction that says to open Show or Hide Modules and remove Manufacturing. In current Bravo Hub ERP versions, that control is deprecated, and hiding a card would not have been a reliable way to protect manufacturing data anyway.

Use the current control that matches the real goal. Domain Settings decides which installed business domains are active for the whole site. Roles and Role Permissions decide which DocTypes a user can access. User Permissions restrict particular records such as a Company or Territory. Workspace configuration controls what appears in navigation. Module Settings changes how a process behaves.

The earlier Show or Hide Modules feature is no longer supported or required from version 15 onward. Do not search for the old Show/Hide Cards control or use a legacy screenshot to configure a current develop site.

GoalCurrent controlNova example
Remove an irrelevant industry for the whole siteDomain SettingsNova leaves Education inactive because it does not run a school.
Prevent a user from opening a DocTypeRole and Role Permissions ManagerThe service coordinator has no Manufacturing transaction permissions.
Restrict records inside an allowed DocTypeUser PermissionsA sales user can work only with an assigned Company or Territory.
Simplify navigationWorkspace visibility and rolesThe service team’s workspace shows Support and Selling shortcuts.
Change module behaviourThe relevant Module Settings pageSelling Settings controls Sales Order behaviour without changing access.

Test with the affected user’s account or assigned roles. Confirm that an unauthorised DocType cannot be opened through search or a direct route, not merely that its workspace card is absent. A hidden shortcut is a cleaner interface; a denied permission is access control.

Current Bravo Hub ERP Workspace list used when reviewing navigation visibility

The old Show or Hide Modules option is missing

Section titled “The old Show or Hide Modules option is missing”

The feature is deprecated on current versions. Identify whether the requirement concerns domains, permissions, record restrictions, workspace navigation, or module behaviour, then use the matching current control.

Section titled “A hidden workspace is still accessible through search”

Workspace visibility does not replace DocType permissions. Remove the inappropriate role or permission and test the direct DocType route.

A user has the right role but sees too many records

Section titled “A user has the right role but sees too many records”

Use User Permissions or document-specific permission logic to restrict linked records such as Company or Territory.

Can Module Settings hide a module from one user?

Section titled “Can Module Settings hide a module from one user?”

Module Settings changes process behaviour. Use roles and Workspace configuration for user-specific access and navigation.

A hidden workspace removes a navigation surface. Server-side role and record permissions must protect the data.

Should old sites keep using Show or Hide Modules?

Section titled “Should old sites keep using Show or Hide Modules?”

Plan a move to the current controls before upgrading or maintaining the configuration. Verify the exact supported behaviour on the site’s version.

It helps readers who find older instructions understand why the control is missing and where to configure the intended outcome now.