07 · Customers & people

This chapter covers two related but distinct sections:

• Customers (/customers) — the customer-360 view of an external company, aggregating contacts, projects, RMM devices, assets and tickets.
• People (/people) — the internal HR module for staff.

These are different from Users (/admin/users) which are login accounts — see Users & access.

Customers

/customers lists every customer (company) your tenancy works with. The customer detail page aggregates records from CRM and the rest of the platform.

Layout

+--------------------------------------------------------+
|  Customers.                            [+ New customer] |
+--------------------------------------------------------+
|  Company        Primary contact     Phone               |
|  Acme Ltd       Jane Smith          020 …    [Open][…]  |
|  Beta Co        —                   —        [Open][…]  |
|  ...                                                     |
+--------------------------------------------------------+

📷 Screenshot placeholder: screenshots/customers-list.png

The list has no tier or status filters — it's a flat alphabetical table with Open, Edit and Delete actions per row.

Customer detail

The customer page is a single scrolling page of cards (not tabs):

• Header card — primary contact name, email, phone, project and ticket counts, and the customer's notes
• Attachments — uploaded documents
• Contacts — linked CRM contacts; + Add contact here creates a CRM contact linked back to this customer
• Projects — every project linked to this customer
• RMM devices — endpoints enrolled under this customer's installer
• Assets — tracked assets owned by this customer
• Tickets — the 50 most recent helpdesk tickets

There is no Invoices card on the customer page in this build.

Creating a customer

Click Customers → + New customer. The form captures: company name (required), contact name, contact phone, contact email, and notes. If you fill in a contact name or email, a matching CRM contact is created (or re-linked) automatically so you don't have to retype the person in the CRM.

A customer record has no tier, owner, support-contract or contracted-hours fields.

Editing and deleting

Use Edit on a row to change the name, primary-contact fields or notes. Renaming a customer propagates the new name to the company field of every linked CRM contact. Delete removes the customer; linked projects become unassigned.

People (HR)

/people is the platform's HR module. It is admin-only and covers the employee directory plus departments, leave, payroll, reviews and onboarding/offboarding workflows.

Layout

+--------------------------------------------------------+
|  People.   [Departments][Leave][Payroll][Reviews]      |
|            [Workflows]              [+ Add employee]    |
+--------------------------------------------------------+
|  [Active][On leave][Terminated][All]                    |
|  [Department ▾]  [Search name, email, title…]           |
+--------------------------------------------------------+
|  Name      Email   Department  Job title  Type  Status  |
|  Emma Lee  …       Helpdesk    Lead       …     Active  |
|  ...                                            [View]  |
+--------------------------------------------------------+

📷 Screenshot placeholder: screenshots/people-list.png

The status pills (Active / On leave / Terminated / All) and the department dropdown filter the list; Active is the default.

Person detail

The employee record (/people/employees/[id]) covers name, email, phone, job title, employment type, department, manager, start/end dates, compensation, status, plus leave requests, leave balances and payruns.

Adding a new staff member

1. Click + Add employee (opens /people/employees/new).
2. Enter first name, last name, email and start date — all four are required.
3. Fill in job title, employment type, department, manager and compensation as needed.
4. Save.

This creates an HrmEmployee record and fires the onboarding workflow. It does not send an invite email or create a login — Users (login accounts) are managed separately under Admin → Users. An employee record can be linked to a User account via the org-chart editor (see Employees).

Time off

Leave is managed under People → Leave. Employees have leave requests (with a type, dates and status) and per-type leave balances; requests are approved or rejected by an admin. See the Leave section of the People module for the full workflow.

Distinctions at a glance

	What it is	Where it lives
Customer	An external company you serve	/customers
Contact	A person at a customer	/crm (or customer's Contacts card)
Employee	An internal staff member (HR record)	/people
User	A login account	/admin/users

An employee can be linked to a User login account. A customer's employee is usually a Contact; if they need portal login they also become a User with a "portal user" role.

See also

• CRM — contacts and deals
• Employees & org chart — self-service and org tree
• Admin → Users — login accounts
• Billing — invoices per customer