Platform Overview β How Plenix Modules Connect
Understand how the Plenix modules relate to each other and which ones you should set up first.
What is Plenix?
Plenix is a unified business management platform β a single system where your CRM, ticketing, billing, HR, accounting, inventory, IT monitoring, and more all live together and talk to each other. Rather than managing 8β10 separate tools, you manage everything in one place.
The core concept: Everything connects through CRM companies
The central entity in Plenix is the company in your CRM. Almost every other module links back to a company record:
- A ticket belongs to a company (your client)
- An invoice goes to a company
- A device is monitored on behalf of a company
- A contract is held with a company
- An employee works for your company (the tenant)
Understanding this relationship is the key to understanding how the platform flows.
The modules and how they connect
Service Desk (Ticketing)
Your central support hub. Clients submit requests, your team triages and resolves them.
Connects to: CRM (clients), SLA (response targets), Knowledge Base (articles), Portal (client self-service), Billing (time-based invoicing), Automation (routing rules).
CRM & Sales
Track companies, contacts, deals, proposals, and the sales pipeline.
Connects to: Billing (generate invoice from a won deal), Service Desk (view tickets per client), Customer Success (health scores), Monitoring (devices per client), Contracts (SLAs per client).
Finance & Billing
Create invoices, manage recurring billing, handle subscriptions.
Connects to: CRM (who to invoice), Accounting (posts journal entries), Printer Monitoring (auto-generates page count invoice lines), Contracts (contract-based billing), Timesheets/ERP (billable hours β invoice).
Accounting
Bank reconciliation, VAT, journals, chart of accounts.
Connects to: Billing (all invoices and payments flow here), HR/Payroll (payroll journal entry), Purchasing (supplier invoices).
Device Monitoring & RMM
Monitor device health, run scripts, manage patches, open remote sessions.
Connects to: Service Desk (auto-create ticket from alert), CRM (devices belong to a client company), Printer Monitoring (separate sub-module for print fleet).
Printer Monitoring
Track toner, page counts, and printer health across your managed print fleet.
Requires: Gateway agent on the printer's network (see Set Up Printer Monitoring).
Connects to: Billing (auto-generates page count invoice lines), CRM (printers belong to a client).
HR & Payroll
Employee records, payroll runs, leave, expenses, shifts.
Connects to: Accounting (payroll journal entry auto-posted), ERP/Projects (resource allocation), Calendar (leave and shifts visible).
Field Service
Work orders, dispatch board, preventive maintenance, permits to work.
Connects to: Service Desk (work order from a ticket), CRM (client site), Calendar (scheduled jobs), Billing (time logged on work orders β invoice).
ERP & Projects
Complex project management, timesheets, budget tracking.
Connects to: Billing (billable hours β invoice), HR (resource allocation), Accounting (cost tracking), CRM (client project).
Compliance & Legal
Audits, incidents, risk register, QHSE training; legal matters, court dates.
Connects to: CRM (client-linked matters), HR (employee training), Documents (evidence and contracts).
Customer Success
Health scores, NPS surveys, structured onboarding plans.
Connects to: CRM (per-company health), Service Desk (ticket volume affects health score), Billing (overdue invoices affect health), Portal (client onboarding tasks).
AI & Automation
AI assistant, autonomous ticket triage, no-code automation rules.
Connects to: All modules (automation rules can trigger actions in any module based on conditions in any module).
Which modules should I set up first?
For most new tenants, this order works well:
- Company profile & branding β Settings β Branding
- Invite your team β Settings β Users
- CRM: Add your clients β CRM β Companies
- Service Desk: Your first ticket β Service Desk β New Ticket
- Billing: First invoice β Billing β Invoices
- Monitoring: First device β Monitoring β Add Device
From there, enable modules as your needs grow. You don't need to use everything on day one.
Users vs Employees β an important distinction
Plenix has two separate concepts that often confuse new users:
| Concept | Where it lives | What it is |
|---|---|---|
| Platform users | Settings β Users | People who log into Plenix (your staff, agents, managers) |
| HCM employees | HR β Employees | Payroll and HR records for your staff |
A person can be both a platform user AND an HCM employee β but these are created separately. A platform user can log in; an HCM employee record is needed for payroll. To link them, toggle Create platform account when creating an employee, or go to HR β Employees β [employee] β Platform Account.
CRM companies vs Tenants β a key distinction (for MSPs)
If you're using Plenix as your own MSP business platform:
- CRM companies = your clients (businesses you provide IT services to)
- Plenix tenants = businesses that license the Plenix platform itself
These are completely separate. Your CRM clients are NOT Plenix tenants. Managing tenants (provisioning, subscriptions, module access) is a super-admin function handled at the platform level.
Where to go next
Was this article helpful?