Nexora Product Guide

What it is, why teams choose it, RBAC, multitenancy, CRM, pricing, and roadmap

Version 2.0 · June 2026 · https://bullwhip.in

1. What is Nexora?

Nexora is a cloud-native Enterprise Management System (EMS) for growing companies. It unifies people operations (HR, attendance, leaves, payroll), work management (projects, tasks, sprints, timesheets), sales operations (CRM), and internal collaboration (chat, helpdesk, announcements) in one secure, multi-tenant SaaS platform.

Each organisation gets an isolated workspace (tenant) with its own employees, departments, projects, policies, and billing plan. Users sign in once and access only the modules and data their role allows.

Modules live in production today:

2. Why Nexora?

3. Roles and working features

Permissions use the pattern resource:action (e.g. leaves:approve). The UI and API both enforce access.

3.1 Role summary

RoleScopePrimary capabilities
SUPER_ADMINPlatformAll tenants, platform stats, cross-org admin; also operates within own tenant.
ADMINOrganisationFull org settings, billing, permissions, audit logs, employees, all modules.
HROrganisation (people)Employees, departments, shifts, holidays, payroll runs, leave pipeline, recruitment, HR analytics dashboard, full CRM access.
MANAGERTeam / projectsDirect reports and project peers; approvals (leave, attendance, timesheets); Team Monitor; full project boards; CRM create/read/update.
EMPLOYEESelfOwn attendance, leaves, timesheets, assigned projects, helpdesk, chat; CRM leads assigned to them.

3.2 Feature access by role

ModuleEmployeeManagerHRAdmin
DashboardPersonal KPIs, 14-day attendance chartTeam Command Center, team chartsHR analytics, workforce snapshotOrg command center; platform panel (Super Admin)
Attendance clock in/outYesYes + team viewYes + org reportsYes + auto clock-out
Leave apply / approveApplyFirst-level approveFinal HR approvalFull pipeline
Projects / Kanban / time logsAssigned workCreate, assign, approve timeRead org projectsFull
TimesheetsSubmitApproveViewView
Team MonitorRoster, productivity, filtersOrg approvals queue
PayrollOwn payslipRead teamRun payrollFull (plan-gated)
CRM — LeadsOwn assigned leads onlyAll team leads; create, update, enrolAll org leads; full accessFull
CRM — ProductsRead onlyRead onlyCreate, update, deactivateFull
CRM — Orders, Transactions, ActivitiesCreate on own leadsCreate and viewFullFull
RecruitmentReadFull ATSFull (plan-gated: PRO+)
Billing / plan upgradeRazorpay checkout
Audit logsRead (export on Enterprise)
Permission overridesCustom per-user policies

4. CRM module

The CRM is embedded directly in Nexora at /crm and shares all platform infrastructure — authentication, multi-tenancy, RBAC, notifications, and Prisma. No separate login or app is required.

4.1 Lead pipeline workflow

  1. Lead Capture — Sales reps create single leads or bulk-import from CSV/XLSX. Contact is upserted by phone number.
  2. Lead Assignment — Defaults to the creating rep; can be reassigned at creation or later.
  3. Qualification and Follow-ups — Reps log calls, emails, WhatsApp messages, meetings, notes. Follow-up count increments automatically.
  4. Status stages — New > Contacted > Qualified > Proposal > Negotiation > Won / Lost / Junk.
  5. Enrolment (Conversion) — On agreement, rep fills the enrolment form: product, date, initial transaction amount, payment mode, optional proof link.
  6. Orders — Each enrolment creates an order. A single contact can be enrolled in multiple products.
  7. Transactions — Payments recorded per order with partial payment tracking and due amount calculation.
  8. Customers — Contacts with at least one enrolment appear in the Customers tab.

4.2 Role-scoped visibility

RoleLead visibilityDashboard view
EmployeeLeads assigned to them onlySales rep — own pipeline KPIs
ManagerAll leads in tenantManager — team pipeline, revenue, rep breakdown
HR / Admin / Super AdminAll leads in tenantManager-level dashboard

5. How multitenancy works

  1. Tenant record — each company is a Tenant row (name, slug, plan, country, currency, storage quota).
  2. User binding — every user belongs to exactly one tenantId; JWT auth includes tenant and role on each request.
  3. Data isolation — Prisma queries scope by tenantId on all business tables (attendance, projects, leaves, CRM, etc.).
  4. Slug — tenants are addressed by URL-safe slug for branding; optional custom domain field on the model.
  5. Plan enforcementPLAN_LIMITS in @nexora/shared caps users, projects, departments, and feature flags per plan tier.
  6. Super Admin — platform operators use a separate platform context to list all organisations via the admin center.
Row-level security is application-enforced (NestJS services + Prisma filters), not PostgreSQL RLS. Always pass tenantId from the authenticated user, never from client input alone.

6. Pricing (INR, per user)

PlanPlan keyMonthlyYearly (approx.)Key limits
FreeFREE0010 users, 3 depts, 3 projects; no payroll or recruitment
StarterSTARTER199/user1,910/user50 users, 25 projects, payroll
ProPRO499/user4,790/user500 users, unlimited projects, recruitment, custom roles, PRO features
EnterpriseENTERPRISEContact salesContact salesUnlimited scale, SSO/SAML, audit export, dedicated CSM, white-label

Checkout is handled through Razorpay after registration. Razorpay API keys must be configured in the environment for payment to be enabled.

7. Future scope

The following are planned for upcoming releases. See the full documentation at /docs (Section 16) for architecture and delivery timelines.

8. Known gaps and improvement areas

Nexora · Vected Technologies · hello@bullwhip.in · +91-9993006892