Skip to main content

Module Licensing

Module: None (core platform) | Role: Admin (configure modules), Platform Admin (deploy modules) | Licence: Varies by module

Modules are commercial feature gates that control which tools, agents, and capabilities are available to a workspace. Modules use colon notation for sub-modules (e.g., sync:network).

Module Hierarchy​

ModuleDomainSub-Modules
insightUnderstandBase platform (always enabled)
insight:policyUnderstandPolicy intelligence agent team
syncControlAll sync sub-modules
sync:networkControlNetwork management
sync:loadControlLoad management
sync:marketControlMarket participation
sync:fleetControlFleet management
operationsManageAll operations sub-modules
operations:agentsManageAgent CRUD, skill management, team management
operations:communicationsManageCampaign analytics (performance summaries, per-campaign metrics, CSV export)
operations:participantsManageParticipant CRM — roster search, growth KPIs, enrolment velocity, exports, QR posters
operations:hardwareManageHardware management — device estate reads, charger connectivity & maintenance status, OEM stats, support tickets, maintenance-mode writes; org-scoped warehouse figures where enabled
programs:connectManagePartner campaigns — tracked recruitment links, contacts, clicks, campaign analytics (optional A2A enrolment handoff)
programs:affiliateManagePartner codes — referral/promo codes, redemptions + qualified counts (no amounts)
operations:energyManageEnergy operations
operations:financialsManageFinancial operations
platform:holisticsConnectPersonal Holistics integration + map layers it powers
platform:slackConnectWorkspace Slack integration for notifications and DMs
platform:snowflakeConnectPersonal Snowflake integration

Enabling a top-level module (e.g., "sync") grants all its sub-modules.

Modules in the platform: family are enablement gates — they make an integration available to connect, but the user still has to connect it themselves (Profile → Integrations). Default tiers include all platform: modules so any member can connect personal integrations without needing a licence change.

What Each Module Unlocks​

insight (Always On)​

Every workspace gets this — it's the base platform:

  • Simulation tools (create scenarios, add assets, simulate, analyze)
  • Chart and visualization tools
  • Hosting capacity queries
  • Context tools
  • Platform documentation (get_platform_doc)
  • Knowledge vaults (via librarian dispatch tools)

insight:policy​

Policy Intelligence agent team:

  • Policy Explorer (regulatory scanning)
  • Policy Librarian (knowledge vault management)
  • Policy Navigator (watchlist, deadline tracking)
  • Policy Analyst (digests, briefings)
  • Policy Steward (coverage monitoring)

operations:agents​

Agent and skill management:

  • Create, update, delete custom agents
  • Create and manage agent teams
  • Create, update, delete skills
  • Agent team deployment

programs:connect​

Partner campaigns — recruit drivers with tracked links and measure the result:

  • Create and manage campaigns (a free-text name + optional landing_url + optional referral_code; there is no programme catalogue)
  • Bulk-import driver contacts
  • Mint a campaign's tracked /connect/j share link (and per-contact links)
  • Manage status (active / paused / completed — completed is terminal)
  • Portfolio analytics: clicks (ours, real time) and redemptions + qualified (core's per-code counts) over time

Clicks are counted by us the moment a link is followed. Redemptions and qualified come from core's per-code performance and read TBC until the workspace is linked to an ev.energy organisation. No monetary amounts are shown.

A campaign can also launch A2A enrolment tasks (launch_campaign / enroll_user) — a per-driver invite URL over the agent-to-agent protocol, an alternative to sharing links. A task completes when the invited driver accepts the invite on Eve Connect; what they do on Connect afterwards is theirs. The hand-off is the invite and nothing else: no driver credential or account data reaches the recruiting workspace. Campaign stats count accepted invites as invites_accepted; there is no enrolled count.

Full verb reference: Partner campaign & affiliate verbs.

programs:affiliate​

Partner codes — the organisation's referral/promo codes and how each performs:

  • List every code (active and disabled) with its redemptions and qualified counts, share link and QR (no amounts)
  • List individual redemptions (one row per redemption, anonymised)
  • Mint a code (admin/owner only)
  • Rename, retag, or disable a code (admin/owner only — codes are never deleted)

All code reads and writes require the workspace to be linked to an ev.energy organisation; until then the codes screen and the redemptions/qualified figures read TBC. Reads are open to any member; writes are admin/owner only.

Full verb reference: Partner campaign & affiliate verbs.

operations:participants​

Participant CRM for programs, fleets, and sites (terminology adapts by vertical — drivers / residents / participants):

  • Look up an enrolled participant by their exact email address (cycle 1 supports exact-email match only — the upstream system has no name or account-number search)
  • Growth KPIs (total acquired, total activated, activation rate) and monthly enrolment velocity — always computed server-side. Where the underlying source cannot report a figure, the dashboard shows a dash rather than a zero: an unknown and a real zero are different answers, and only one of them is a measurement
  • Roster export as a CSV download link
  • Enrolment QR posters

Privacy by design: Eve only ever handles an opaque participant reference plus a minimised display label — never names, contact details, addresses, or account numbers. Full participant records are viewable only in the Participants pages of the operator console, and exports are delivered as secure download links rather than through chat.

operations:hardware​

Hardware management for an organisation's device estate — vehicles, chargers, solar, and home batteries:

  • Device estate reads: list devices by type with a summary, look up specific devices of any type (up to 50 at once, by the id, serial number, OCPP id or VIN shown on screen), filter the list by status and brand as the results page does, and see OEM / manufacturer stats. The summary and the OEM stats cover every device type or the one the selected tab shows
  • Work queues: find the devices waiting to be set up, whose connection lapsed, that stopped reporting, or that report a fault. The summary gives each queue's exact size, counts what needs attention separately from the setup backlog, and says when a queue can't be measured for a device type yet
  • Charger connectivity and maintenance status, and support tickets (list, raise, re-prioritise, close)
  • Maintenance-mode writes: put a charger into or out of maintenance from the same conversation, with a confirmation step before anything is written. Maintenance mode pauses the charger in ev.energy's operator tools only; nothing changes at the charger, and drivers can still charge
  • Every read and write is tenancy-scoped server-side to the workspace's own organisation — the caller never supplies an organisation id

Warehouse figures (enabled per organisation). For organisations on the warehouse tier, Eve can also answer estate counts, vehicle connectivity, and charger session quality from the data warehouse. These are aggregates only — never a device list or a per-person figure — and are switched on one organisation at a time after an internal data-protection review. This is not a plan limit and there is nothing to upgrade.

platform:* (Integration Enablement)​

The platform: family unlocks the option to connect a third-party integration. They are licence-free by default — every workspace tier includes them — so any member can connect their own credentials in Profile → Integrations without an admin or licence change.

ModuleUnlocks
platform:holisticsPersonal Holistics API key. Enables the "Known charging sites" map layer and Eve queries against your Holistics datasets.
platform:slackWorkspace Slack notifications (auto-connected via OAuth).
platform:snowflakePersonal Snowflake integration for Eve queries.

Note: enabling the module makes the integration connectable; the user still has to complete the connection step. A licensed-but-not-connected integration is a no-op until credentials are provided.

How Modules Affect Tool Visibility​

When Eve or an MCP client connects, the tool list is dynamically filtered:

  1. Base tools from always-on modules (insight) are always included
  2. Tools from enabled modules are added
  3. Dispatch tools from registered agents are included (with four access gates: module, workspace, user visibility, conversation scope)
  4. Locked modules show upsell hints (e.g., "Policy Intelligence is available on Pro plans")

Checking Your Modules​

Ask Eve: "What modules are enabled for my workspace?" — Eve uses get_current_context to show your workspace's enabled modules and available tools.