Modules
The registry of every module in your tenant and the specific permission groups (like “Create”, “Edit”, “Delete”, “View”) available on each one.
What is this?
Each business module in EnOpSy (Forum, Billing, Clients, Drive, and so on) is broken down into one or more permission groups — for example, the Forum module has separate permission groups for “Forum”, “Form Templates”, and “All Submissions”. Each group carries a set of actions (typically Create, Edit, Delete, View) that Roles & Permissions can grant or withhold. This page is where those groups and actions are defined.
Why use it?
You'll come here if you need a permission action that doesn't exist yet — for example, adding a new “Approve” action to a module before you can grant it to a role. Most day-to-day permission management happens on the Roles & Permissions page instead; this registry is the plumbing behind it.
Before you start
- Required role: Owner or Admin.
- Dependencies: none — this page has no enable/disable effect on the modules themselves. For that, see the Module Settings screen instead.
- Warning: changes here define what permissions exist, not who has them. Adding or removing a permission group here can affect every role that references it.
How to open it
Settings › Modules
How to use it
- Open Settings › Modules. You'll see a card per module with its permission count.
- Click a module card to see its permission groups and their actions.
- Click Add Permission to define a new permission group for that module: give it a Display Name, a Slug (lowercase, underscores — used as the internal key), and pick the actions it should support.
- Hover a module card on the main list to reveal an edit (pencil) and delete (trash) icon for modules you're allowed to modify.
- Click Create Module (top-right of the module list) to register a brand-new module: it needs a Module Name and a Slug.
Fields and options
| Field/Option | What it does | Example | Important Notes |
|---|---|---|---|
| Module Name | The human-readable name of a new module. | Inventory Management | Required. |
| Slug | The unique, code-facing key for the module. | inventory | Lowercase, no spaces — required. |
| Display Name (permission group) | Human-readable label for a permission group. | Manage Users | Required. |
| Slug (permission group) | Internal key for the permission group. | manage_users | Lowercase, underscores recommended — required. |
| Available Actions | The specific actions (Create, Edit, Delete, View, etc.) this group can grant. | create, view | Type to search existing actions or create a new one. |
What happens after saving?
New modules and permission groups appear immediately in the list — no refresh is required. They are also immediately selectable when adding a module to a role on the Roles & Permissions page.
Example
To let a role approve forum submissions, first check the Forum module's “All Submissions” permission group for an “approve” action. If it doesn't exist, add it here via Add Permission, then go grant it to the relevant role on the Roles & Permissions page.
Common problems
Problem: A module card shows an orange “Display name not set” warning even though the module is clearly in use.
Why it happens: The module was registered with only a slug and no separate display name configured.
How to fix: This is a data-cleanup item for your EnOpSy administrator/support contact — it doesn't block the module from working.
Problem: Clicking the primary button with required fields blank appears to do nothing.
Why it happens: The form is validating client-side but not yet showing an inline error message.
How to fix: Fill in every field marked with a red asterisk (*) before submitting.
FAQs
- Does deleting a permission group here remove it from roles that already have it?
- Yes — a permission group only exists if it's defined here, so removing it removes the option for every role. Only remove groups you're certain are unused.
- Can I turn a module off from this page?
- No. This page only manages what permissions exist, not whether the module itself is active. See the Module Settings screen for enabling/disabling modules.