Description
Nexus – HR, CRM & Project Management System
Nexus – HR, CRM & Project Management System runs the people, the pipeline, and the projects out of one Laravel application. Employees, attendance, leave and payroll. Leads, deals, quotes, invoices, contracts and support tickets. Projects, tasks, sprints, time and the invoice that comes out the other end. One install, one database, one login.
Feature list
1. Web installer
A guided, six-step first-run wizard. Every address on a fresh copy redirects into it.
- Requirements — PHP version, twelve extensions and six writable paths, each shown pass or fail, with a re-check button. Nothing has been written yet.
- Company — name, currency and timezone. An application key is generated for you.
- Database — host, port, name, user and password, with a Test connection button that verifies before it commits. If the database does not exist, Nexus creates it, provided your database user may.
- Administrator — your account, with the admin role.
- Sample data — an optional twelve-person demo company, on a tick box, so you can walk into a populated system instead of an empty one.
- Review & install — writes .env, migrates, seeds the reference data and creates your account. The log narrates each step and stops exactly where a failure happened.
Nothing is written until the last step: the wizard holds your answers in the session, so an abandoned install can never leave a deployment with a rewritten .env pointing at a database that was never migrated. Once finished, the installer seals itself off and /setup redirects away.
2. Roles, permissions & locations
- Twelve permission sections — employees, attendance, leave, payroll, recruitment, performance, CRM, sales, support, projects, reports, settings. Each is a tick box on a person’s record.
- Seven roles ship — Administrator, HR, Manager, Sales, Project manager, Accountant, Employee. A role is a starting point that sets sensible boxes, not a cage: tick and untick from there.
- Self-service needs no section. Every signed-in person sees their own attendance, leave, payslips, expenses, timesheet, goals and tasks — scoped to themselves, always.
- Approvals need no section either. Anybody with people reporting to them gets an approvals queue for their own reports, without being handed the HR module.
- Projects add per-record access — a developer with no projects permission still opens the two projects they were added to, as viewer, member or manager, and nothing else.
- Deactivating somebody stops them signing in immediately and kills their API tokens with them, without deleting a thing they did. Their name stays on the deals they won.
- Locations — an office, a site, a country. Holidays are declared per location, leave counting skips the right ones, and reports filter by them.
Hiding a menu item is presentation. A person who types a URL they may not have gets a 403.
3. Dashboard
Assembled from what you are allowed to see. A sales user gets pipeline and revenue; an HR user gets headcount and who is off today; a project manager gets delivery. Nothing is computed for a section you cannot open, so a narrow account is a fast page.
- Mine — everybody gets this one: today’s clock state, leave balance, tasks due, and what is waiting on you to approve.
- People — headcount and its change, joiners and leavers by month, probations and contracts ending inside 30 days, documents about to expire, present and late today, worked and overtime trends, pending leave and who is off, payroll gross and net by month, the candidate funnel and today’s interviews.
- Commercial — open pipeline with its weighted value and its shape by stage, activities due and overdue, deals won and lost by month; invoiced against received drawn on one money axis, never two, so the gap reads as the collection lag it is; outstanding and overdue balances with the five worst invoices; ticket volume and SLA breaches.
- Delivery — active projects, tasks created against completed per week, overdue and due-this-week, hours logged this week against last, unbilled hours waiting to be invoiced, open issues by severity and the milestones coming up.
Headline figures show their change against the previous period, because a number without a direction is decoration.
4. People
- Employees — the directory, and the record every other HR screen hangs off. Manager, department, designation, location, hire date, employment type, probation end, salary, contact and bank details.
- Employee codes are generated from a prefix and never reused, so a code points at one person for the life of the system.
- The record has tabs — profile, attendance, leave, documents, assets, salary, goals and reviews. Each is the module’s own data filtered to this person; there is no second copy anywhere.
- Departments with an optional head and an optional parent, and designations as job titles. Neither can be deleted while somebody is in it.
- Org chart — the reporting tree drawn from the manager field, clickable through to the person.
- Leavers — set a leave date and the person drops out of headcount, rosters and pay runs while every payslip, approved leave and won deal stays readable.
5. Onboarding, documents, announcements & assets
- Onboarding checklists — build a template once as a list of tasks, assign it to a starter, and the due dates are counted from their start date. A candidate hired through recruitment can have one attached at the moment they are converted.
- Documents — contracts, certificates, ID copies, right-to-work papers, each with a category and an expiry date. The overview filters to expiring within 30 days or already expired, with counts at the top, so a visa or a certification does not lapse quietly.
- Announcements — company notices, optionally scoped to a department or a location, optionally pinned, shown on the dashboard of the people they are aimed at. Drafts appear to nobody.
- Company assets — laptops, phones, keys, cars. Assign from a date, return on another; every assignment is kept, so the asset shows everyone who has held it and the person shows what they currently hold. That second list is the one you want on a leaver’s last day.
