Heyllave organizes tasks into modules. Modules share references and events, but each keeps its own records, permissions and states. Completing an action in one module does not mean the other steps are complete.
Choose the workflow you need
| If you need to… | Start here | It can continue in… |
|---|---|---|
| Handle an appointment | Bookings and calendar | Customer, work order, document |
| Record and complete service work | Work orders | Entities, catalog, documents, invoicing |
| Track items | Catalog | Inventory, work orders, storefront |
| Sell from a public site | Storefront and published catalog | Order, stock, payment and follow-up |
| Charge or record a payment | Invoicing | Document, ledger and reports |
| Notify an external tool | Events and webhooks | Automation configured by your team |
Available connections depend on enabled modules, configuration and your permissions.
Module dependencies
| Module | Requires | Can work with |
|---|---|---|
| Catalog | Entities | Inventory, work orders, storefront and invoicing |
| Conversations | Entities | Agents and notifications |
| Agents | Conversations | Tools allowed by the agent configuration |
| Storefront and orders | Catalog and sites | Stock and the configured payment provider |
| Invoicing | Documents | Work orders, payments, accounts and ledger |
| Work orders | Invoicing, documents and entities | Catalog, calendar, bookings and reports |
| Bookings | Calendar | Services, resources, customers and notifications |
| Dashboards | Documents | Metrics published by enabled modules |
This table describes product-declared dependencies. “Can work with” connections require the relevant workflow and settings; they are not all enabled automatically.
One cross-module workflow
- Create or find the customer in Entities.
- If the visit needs a time slot, create a booking and check service and resource availability.
- Record the work in Work orders. Add catalog items when needed; check quantities and location before confirming stock movements.
- Generate a document from the workflow that owns it. Check whether it is a draft, published or awaiting signature.
- Issue the invoice and record payment after you receive it. Heyllave stores the record; recording a payment does not transfer money by itself.
See the guides for bookings, work orders, receiving items, documents and invoices for each screen’s steps.
Settings and combinations
Before enabling a workflow, review these dimensions. Your workspace settings show the values available to your modules:
| Dimension | Options to check | What changes |
|---|---|---|
| Module | Enabled or disabled; required dependencies | Which screens and actions are available |
| Instance | One or multiple instances, when supported | Which set of records you are using |
| Permissions | Read, create, edit, approve and administer | What each person can do |
| Capability | Feature switches, such as time tracking or SLA when shown | Which additional module options are available |
| Location | Locations enabled for items and stock movements | Where stock is read or recorded |
| Channel | Public site, portal, conversation or configured integration | How customer interaction starts or continues |
| Automation | Configured rules, reminders, events and external destination | Which notices or actions run afterward |
There is no universal combination: you can use bookings without work orders, or manage work orders without publishing a storefront. Enabling a feature does not grant permissions automatically.
If an action is missing
- Confirm that you are in the right workspace and module instance.
- Ask an administrator to check the module and its dependencies.
- Check the feature switch and your role separately.
- Check whether the record has reached a state where that action is unavailable.
- Review the module’s activity or audit history for the related change.
Next
Understand modules and settings → · Browse available events →