Skip to main content
A module is a part of Mercora that your workspace can switch on or off: a surface like Contracts or P&L, a workflow like Hedging, or a shared capability like Copilot. Modules let each workspace use exactly what fits how it works, and keep everything else out of the way. Modules apply to the whole workspace. Whether a particular person can then see and change a module’s data is decided by their role. See How modules and permissions combine.

Turn modules on or off

Before you start: only workspace admins can change modules. Everyone else can see which areas they have in the sidebar; ask your admin to turn a module on.
1

Open the Workspace settings

Go to Settings, then under Workspace click Workspace.
2

Find the Modules section

Modules are grouped into Core app, Workflows and Shared capabilities. Each one has a short description of what it controls and what turning it off hides.
3

Flip the switches you need

Turn each module On or Off. The page shows “Unsaved changes” until you save.
4

Save

Click Save changes. Click Reset instead to discard your edits.
The Modules list with the Core app group and modules nested under Trades

Modules in Veltana Commodities SA. Shipments (trade tab) and Trade financials nest under Trades, with Vessel Tracking and Cost & income plan one level further down.

Some modules sit under a parent module. A child module only works while its parent is on: when the parent is off, the child’s switch is greyed out and reads “Requires” followed by the parent’s name. Turning a parent off also turns off the modules under it. For more on the rest of this page, see Workspace settings.
Turning a module off hides it. It doesn’t delete the data. For several workflows, work already in progress stays available to finish after the module is turned off, as noted in the tables below.

Core app

A child module marked “On” only takes effect once its parent is on. For example, the three reports are ready as soon as an admin turns on Reports.

Workflows

Each workflow is turned on separately, and its access is granted separately in each role.

Shared capabilities

See Integrations for how to connect these systems.

How modules and permissions combine

A module being on doesn’t give everyone access to it. To use a part of Mercora, a member needs both:
  1. The module turned on for the workspace, and
  2. A role that grants at least View on the matching permission (and Edit to make changes).
For example, if Counterparties is on but a member’s role has Counterparties set to None, that member doesn’t see Counterparties in the sidebar. If the role grants Counterparties but the module is off, they don’t see it either. A few areas collect work from several places and appear when any one of them applies:
  • Home appears if the member can use either the overview cards (Dashboard module and permission) or the Copilot (Copilot module and permission).
  • Inbox appears if the member has access to any enabled workflow that sends items there: documents, Deal Capture, Freight Rates, Hedging, or automation results.
  • Upload appears if the member can upload documents, or can upload freight rate sheets through Freight Rates.
See Roles and permissions for the full list of permissions.

Next steps

Roles and permissions

Decide who can view and change each area you turned on.

Members

Invite your team and give each member a role.

Workspace settings

Company profile, reporting currency and the rest of the Workspace page.