Understand Modules

Review module purpose, actual access, dependencies and permitted next steps.

Before you start

  • Use the correct company and an active account with permission for this workflow.

Where to go

Modules → Module Center

Audience

Business owners reviewing company module access.

Permissions

  • Use your current account role; a Help link does not grant permission.

Workflow

  1. Open Modules → Module Center. Check the selected company and the current server-provided entitlement. A catalog card is not proof that a workflow has shipped.
  2. Review the nine keys: manager (company operations), track (field tracking), b2b_marketplace (company requests), f2b_marketplace (independent professionals), external_marketplace (External buyers), ai_chat (configured AI assistance), auto_dispatch (work assignment), auto_operator_routing (operator routing), business_website_core (website foundation).
  3. Read dependencySummary, setup and terms for this company. Complete the displayed prerequisite with the responsible owner; dependencies and allowed actions come from the current server result.
  4. Available means you may review an option; free means included; contracted means granted under the business contract. Current enabled access and released workflows still determine what can be opened.
  5. For trial_active, paid_monthly, paid_yearly or enterprise_provisional, use the displayed interval and terms. Do not assume a price, renewal, automatic conversion or trial duration.
  6. For paused or expired, review only the offered remediation. For dependency_blocked, resolve the displayed prerequisite. For compliance_suspended, contact the responsible administrator without requesting private review details.
  7. Configuration unavailable or not released means the live screen cannot run. Keep its explanation visible and read Help. Manager or Track catalog presence does not prove migration or rollout completion.
  8. Use a permitted action only after reading required terms. Disabled payment controls retain their reason. Opening Help does not start a trial, charge a card or activate a module.

Expected outcome

Read the current saved state in the workspace after the permitted action; Help does not perform or verify the action.

Troubleshooting

A card exists but the feature cannot open
Check current enabled access, dependencies, rollout, role and configuration independently. Escalate the displayed blocking reason to the responsible owner.