Modules
Not every project needs every feature. A small one-day workshop does not need an exhibitor floor plan, a conference abstract review system, or a streaming setup. Modules let you turn feature areas on or off per project so each event's admin portal reflects exactly what that event does.
What modules control
A module is a named feature set. Enabling a module makes that area's navigation items, configuration screens, and data tables visible in your project. Disabling a module hides them without deleting any data — if you re-enable a module later, your configuration and records are still there.
The Core module is always on. It covers the project itself, tasks, documents, approvals, meetings, forms, people, roles, QR codes, and reports. All other modules are optional.
Available modules
| Module | What it adds |
|---|---|
| Exhibition | Exhibitor management, floor plans, tiers, allocations, entitlements |
| Programme and Submissions | Talks, sessions, the schedule builder, reviews, speaker management |
| Registration | Registration types, add-ons, group registrations, waitlist, check-in |
| Financials | Orders, invoices, payments, credit notes, budgets, deals |
| Engagement | Networking, Q&A, polls, surveys, attendee notifications |
| Gamification | Badges, challenges, leaderboards, and point systems |
| Streaming | Live streaming for virtual and hybrid events |
| Content and Communications | Knowledge base articles, email builder, content pages |
| Integrations | EventsAir, SharePoint, and third-party sync |
| CPD / CE | Accreditation, credit tracking, certificates, and AMS sync |
How modules are enabled
You can enable modules during project creation, or later from Project Settings > Modules. When you enable a module, ema offers three setup options:
- Defaults — applies a standard starting configuration.
- Configure — asks a few short questions and builds the configuration from your answers. For example: "Is this a paid or free event?" or "Will you accept abstract submissions?"
- Clone — copies the configuration from another project in your organization. Useful when you run the same event format year after year.
Disabling a module is reversible. Your data is preserved.
If a feature is not showing up, check whether the relevant module is enabled. Module state is checked when pages load, so enabling a module takes effect immediately — no need to reload or republish.
The effect on navigation
Each enabled module adds its own section to the project sidebar. The more modules you enable, the more the sidebar grows. For smaller events, keeping only the relevant modules enabled keeps the interface focused and easier for your team to navigate.
Modules and client access
Module state also affects what clients can see in the client portal. A client invited to view a project sees only the areas their project has enabled. An exhibitor portal, for example, is only available when the Exhibition module is on.
Enable and disable modules for a project.
How projects and organizations relate.