A module you build on your account can be shared with all Intum users. After submission and acceptance by an administrator, the module will automatically appear on all accounts — no need to enable or install anything.
Why Share Modules?
A few ideas of what you can do:
- Build an integration with your external system (ERP, warehouse, CRM) and share it with clients
- Create a report, dashboard, or tool useful to a broader audience
- Prepare a ready-made module as a service — e.g., an industry-specific solution for a particular niche
- Extend existing Intum modules with missing features (e.g., an additional view in CRM or Helpdesk)
Public modules are a way to build solutions on the Intum platform and share them with others.
How It Works
The entire process looks like this:
- You create a module on your account (connect a CMS page, Noe application, or knowledge base)
- You test and refine it
- You submit it for publication — choosing a public code under which the module will be available
- The system administrator reviews the submission and accepts (or rejects) it
- After acceptance, the module is visible and available on all accounts
Submitting for Publication
Go to the module details (Platform - Modules — click on the module) and click the Publish button.
A form will appear with one field — public code. This is the URL path under which the module will be available on other accounts (e.g., sales-report = available at /sales-report).
A few things to keep in mind:
- The code cannot conflict with existing system modules (organize, mail, crm, etc.)
- The code cannot be taken by another published module
- If the code is unavailable, the system will ask you to change it
After submitting, the module is cloned to the system account with an inactive status. It waits there for administrator approval.
What Happens After Acceptance
The administrator changes the module status to active. From that point on, the module appears in the menu on all accounts. No need to enable anything — public modules are available immediately.
Cloning Modules
Regardless of publication, you can clone your modules. The Clone button in the module details creates a copy (including the connected site, application, or knowledge base) under a new code. Useful when you want to test changes without touching the original.
Good to Know
- A published module is a copy — changes to your original module do not affect the public version
- One module = one public code. If you want to publish several variants, submit them separately under different codes