Parties
Customers, clients, companies, and contacts — CRM-style records per Business.
Last updated 2026-09-01
What it is
Party modules store the people and organizations you work with. Each type is a separate resource with its own list, detail, create/update, image, and delete endpoints — all scoped to the active Business.
| Resource | Typical use |
|---|---|
| Customers | Buyers or accounts you sell to |
| Clients | Client relationships (parallel party type) |
| Companies | Organization records |
| Contacts | People linked to your CRM workflow |
Who can access
Access follows role permissions (customers, clients, companies, contacts). Integration credentials need matching scopes and CRUD actions.
How to
Create and maintain
- Open the relevant module in the Business UI
- Create a record with required fields (e.g. customer name); optional email, address, status
- Upload an image where supported (often a single image per record)
- Update fields or soft-delete when the party is no longer active
Customer example fields
- Required: name
- Optional: email, address, status (active/inactive), images
Constraints
- Soft-delete is common — deleted parties leave active lists but may remain recoverable only via support processes
- No built-in CSV export UI/API — request exports via support if required
- Party types are separate; do not assume automatic sync between customers and clients