CNV ConnectTwelve modules, one workspace
Same people, same permissions, same reports. Switch a module on and it inherits the directory you already built — there is no second system to keep in step.
Time clock & attendance
GPS and Wi-Fi verified clock-in, live attendance board, corrections with an approval trail.
Scheduling
Build the week in a grid, copy last week, publish open shifts staff claim from their phone.
Forms & checklists
Safety forms crews fill in on site — and rules that block a shift until they are done.
Task management
List, kanban, gantt, calendar and workload views over the same tasks, with subtasks and files.
Approvals
Design a request form, route it through the right signatures, keep the audit trail.
Team chat
Channels, direct messages, files and pinned notices, with a company-wide room kept in sync.
Help desk
Tickets with SLA clocks, assignment rules, reply templates and a widget for your website.
People & HR
Employee records, contracts and renewals, org chart, leave requests and yearly balances.
Assets & equipment
What you own, who holds it, stock counts — plus the subscriptions you pay for every month.
Reports
Attendance, headcount, contracts and assets, computed from the same records your teams file.
Automation
"When this happens, do that" — notify, assign and update without anyone remembering to.
Mobile app
The whole deskless side of the product: clock in, submit forms, claim shifts, chat, approve.
The connections are the point
Most tools stop at their own edge. These do not.
| When this happens | This follows, automatically |
|---|---|
| A leave request is approved | The days appear on the monthly timesheet and the person is no longer counted absent |
| An attendance correction is approved | The record is rewritten and the day is re-evaluated, with the trail kept |
| A new employee is invited | They join the company chat room, inherit their department's shift, and appear in headcount |
| A ticket needs work next week | It becomes a task, linked back to the ticket, in the assignee's list |
| A form is marked required for a site | Clock-in on that site stops until it is submitted, and the submission is filed against the shift |
| Somebody leaves | Disabling them frees a seat, ends chat membership, and surfaces the assets and accounts they still hold |
Built to be run by an operations team, not an IT project
Roles and permissions
Every page has a permission. Roles bundle them; menus and the server both enforce them.
Web and mobile
Administration on the web, the day-to-day on the phone — one account, one directory.
Open at the edges
Scoped API keys and signed outbound webhooks when another system needs the data.
Multi-workspace
One person can belong to several workspaces and switch between them without a second login.
Get your whole team on one system this week
The Free plan covers 10 users with every module switched on — no card, no sales call, no migration project.
Free forever for 10 users · no credit card · set up in an afternoon