# Connect modules to each other

Your modules can share records and work together, like a job that knows its crew and its costs, without ever being tangled together.

Your **Field Services** module knows the jobs. **HR** knows the people. **Accounting** knows the costs. Wouldn't it be nice if a daily report could pick a crew from HR and post its hours to Accounting? It can. That's a **module connection**.

## How modules connect

Modules never reach into each other's code or tables. Instead, a module **offers services**, like *list the active employees* or *post this cost to a job*, and other modules **use** them. The platform carries the call, checks the person's permissions on the way, and keeps everything inside your workspace.

| A module can… | For example |
|---|---|
| **Offer a service** | HR offers *list employees*. |
| **Use another module's service** | Daily reports use HR's *list employees* to fill the crew. |
| **Use "any module that provides…"** | A form that needs a list of projects works with whichever projects module you have. |
| **Listen for events** | When a job is closed in Field Services, Accounting sends the invoice. |

## Required or optional

Each connection says whether it's **required** or **optional**:

- **Required:** install the module and the one it needs comes along automatically.
- **Optional:** it works without it, and does more when it's there. A time card module might work alone, and fill in job names when your jobs module is installed.

## See the connections

On any module's Marketplace page, the **Works with** tab shows what it uses and what uses it. Your AI assistant can draw the whole map for your workspace: ask it to *show how my modules are connected*.

## Building one?

Just tell the Module Builder: *"pick the crew from our HR module"*. It finds the service, declares the connection and checks it. The details are in [Services: how modules call each other](article:eea37a13-648b-4366-92bb-1b437221765b) and [Events and live updates](article:db90fa30-3ef5-42e9-bc1a-9fee6fe3034e).


Source: https://datavisions.ai/docs/creators/connect-modules-to-each-other
