What's shipping, as of today

Business Module and CRM settings Open links use hash href anchors only; no routerLink or click interceptors.

Business Module and CRM settings links use routerLink plus Router.navigate with queryParams instead of navigateByUrl on combined URLs.

Linked settings and module settings Open links route reliably under hash routing via navigateByUrl.

Linked settings Open links navigate via hash hrefs; route targets use single-path router commands.

Module detail Linked Settings Open links use Angular router links with query params for reliable tab deep links.

Lifecycle uniqueness, issue and party/GST guards, decision ledger, export artifact audit trail, and pilot library qualification on the Quote Engine API.

CRM Settings cards and sidebar links open the right tab; child settings routes match; Back respects returnTo.

CRM business-module policy fields are editable on Application Settings and enforced on staff lead create and lead conversion.

Setup wizard and linked settings preserve return navigation; keyboard users can open linked settings with Enter; wizard fix actions match module detail resolution targets.

New estimates are built in a dedicated workspace with prospect-scoped CRM data, rich terms and templates; CRM module configuration separates required setup from optional enhancements and names every fix action.

The link in the personal-email verification email now opens a page that confirms the address.

Every report and document can be previewed before downloading, sales documents follow the new professional layouts, command centers and maps match the approved designs, and opportunities move forward from one simple stage bar.

Application Settings is now a guided settings workspace, command centers show real monthly trends and a shared India map, and Purchase and CRM gain new home views.

Tools → Email and other tool workspaces fill the routed column, remaining shell chrome uses mapped Material icons with wrapping labels, and Pilot also ships the Purchase Command Center and print-paper tokens already on main.

Pilot HR onboarding and performance collectors now fail closed on missing evidence, search dropdowns line up with the text boxes beside them, and module More menus close when you click away.

Pilot module homes now use the approved contextual icon treatment across KPI cards, section views and analytics panels instead of generic or text-only card chrome.

Pilot module homes now expose their approved operational hierarchy, certified queues and honest unavailable states instead of sparse, fragmented or duplicate navigation views.

Pilot navigation, command centers, governed CRM capture and API request handling now match the approved app-wide UAT contract under sustained authenticated use.

The remaining approved module, CRM, territory, location, return-navigation, report and onboarding requirements are reconciled for Pilot validation.

Inventory, Knowledge Base, Library and Site Survey now open dedicated, full-width command centers with authoritative module-wide data and the approved analytical composition.

Week view now exposes the same complete, actionable calendar-item treatment as Month and Day, grouped by date without capping or hiding records.

CRM day-calendar entries now open the approved communication-notes and next-follow-up form for both lead and deal commitments, closing the final live Pilot mismatch found during the app-wide acceptance replay.

The approved app-wide tabbed interface now reaches the operational pages, calendars, shared quick actions, location-aware CRM records and full-width command centers required for Pilot acceptance.

Operational overviews now match the approved resource hierarchy with centered workspaces, prominent semantic KPI icons, denser ledgers and reliable module-tab ownership.

Module workspaces now use the approved tabbed navigation and consistent controls, while legacy imported CRM references no longer break sales command-center views.

Support Chat inbox aggregation now uses the MongoDB stage supported by the deployed Pilot server while preserving the same unread and activity projections.

Founders and sole proprietors can now use the same isolated, email-verified private Vault as eligible directors without being treated as employee-directors for payroll.

The Pilot UAT graph now keeps its opening stock in one warehouse and presents the issue-adjusted ledger balance as the current quantity.

Pilot UAT seed snapshots now protect the complete database against drift without loading every business record into memory.

Revenue KPIs now rely on posted billing evidence, and managerial employment drafts can be corrected through a crash-safe, Pilot-only policy repair.

Salary-advance and Fleet decisions now require immutable evidence, and Pilot-to-Production HR conflicts can be resolved only through an exact reviewed, rollback-capable merge plan.

Managed performance actuals now stay evidence-backed, HR promotion previews verify typed dependencies and role authority, and the Production deploy path has stronger isolation and identity checks.

Pilot can now retire only the exact duplicate reminders left by the legacy Perfex manifest while preserving every business record and retaining complete disposition evidence.

Commercial modules now use the approved icon-led tab shell, CRM follows the prospect-first lifecycle, locations share one governed authority, and customer reports retain their approved print geometry.

Onboarding, employee payments and Propulsive KPI evidence now use one governed launch boundary, with permanent Pilot scoring exclusions and an encrypted HR promotion manifest.

Propulsive's approved L1-L7 pay-band corrections can now be applied safely to Pilot's standalone MongoDB with protected recovery evidence.

Employee performance, fleet logging, privacy controls, the Pilot order-to-cash rehearsal and Quote Engine Phase 2 now use clearer workspaces and stronger audit evidence.

Onboarding audit rows, attendance provenance, movement locks, privacy retention and final-settlement dues now remain reliable across the complete employee lifecycle.

The Onboarding page keeps its shared enterprise table mounted during asynchronous loading so returned employee rows render without waiting for content projection to be recreated.

Attendance breaks, inactivity locks, onboarding, Digital IDs, resignation terms and employee documents now enforce their authority at the API boundary and retain reviewable audit evidence.

Offer letters, payroll payments, TA reimbursements, RACI, session controls, attendance and operational KPI actuals now share stronger authority, audit and retry guarantees.

CRM now matches the approved compact hierarchy with six direct daily-work tabs and grouped access to every other destination.

CRM now uses a single icon-led tab workspace across every route, with module administration kept in a permission-gated Settings area at the upper right.

CRM now supports clean contact-to-customer progression, territory-scoped work, historical prospect qualification, compact capture, and the imported Perfex pilot dataset.

Salary advances now post from an approved funding account, recover only from available pay, carry unpaid balances forward, and remain traceable through payroll and employee self-service.

Commercial terms, addresses and payment details are easier to read across sales and purchase documents.

Estimate authors now add itemised and special discounts explicitly, while zero-discount records keep those controls and report fields hidden.

Employees can open a focused salary-advance workspace from their profile, while HR device and inactivity policies now reach already-open sessions safely.

The Sales estimate detail now reloads the selected record on every route change, so itemised and special discounts from a prior estimate cannot remain visible on a zero-discount estimate.

Estimate details now reload the selected record whenever its route changes, preventing commercial columns and totals from a prior estimate from remaining on screen.

Estimate and Proforma outputs hide unapplied discounts, render authored terms cleanly, and present part payments as a complete final audit table.

Pilot TA receipts now resolve against one valid public origin even when the configured browser allowlist contains several comma-separated URLs.

Employment Documents keeps its heading and guidance readable at phone widths while actions wrap into their own row.

Historical probation metadata can prepare a confirmation draft while a missing canonical Employment History event remains visibly blocked for independent resolution.

HR can reconstruct, approve, issue and acknowledge appointment letters, probation confirmations and professional-service agreements with controlled numbers and immutable issued records.

All report ribbons are removed. Status appears as plain document metadata, and branding previews open at the top with accurate page sizing.

Commercial documents follow the approved report skeletons with printable corner ribbons, consistent branding, safe continuation pages, and a responsive preview. Party Directory and Customer 360 now expose onboarding email actions.

HR can issue controlled disciplinary and recognition documents, employees can see proposal-only KPI evidence on Home, and customer reports show discount columns only when positive persisted discount money exists.

Branding now renders the selected commercial report skeleton in the dedicated right preview pane, at a usable scale and with the same header, discount, transaction, payment and footer structure as generated PDFs.

New-hire probation, confidential offer delivery, structured employee designations and performance evidence now share enforceable source and approval controls without inventing production scores.

Commercial PDFs now follow the approved estimate, proforma, sales-order and delivery-challan structures, with governed branding, color or monochrome output, conditional discount evidence and safe multipage pagination.

Estimate discounts now appear only when backed by positive persisted money, while HR identity, Digital ID, RACI, multi-establishment policy and employee-lifecycle controls are hardened for the pilot rollout.

The Professional GST Proforma now uses even A4 page margins and keeps the receiving-bank, payment-status and signatory details as the final report block after commercial terms and notes.

The proforma uses a more compact header with source evidence in the document body, and estimate/proforma detail tables show item discount percentages only when at least one line has an applied discount.

Leads can be captured quickly in a centered modal, calendar follow-ups can be completed and rescheduled in place, parties are searchable across connected modules, and commercial reports now follow the approved structures with installation-wide branding and conditional discount evidence.

Large CRM forms now show a clear selected section boundary, controls follow one size and focus contract, record actions open in centered dialogs or full workspaces, and tab and view choices carry relevant icons with accessible selected states.

The guarded pilot import now preserves lead and follow-up ownership for staff who have one verified active employee match by email, phone or exact name, while leaving unresolved identities unassigned for review.

Tab navigation now follows one shared Analytics-style pattern throughout the app, with relevant icons, clearer selected state, keyboard movement and mobile overflow guidance.

The registered Propulsive vehicle now has a guarded, reversible pilot data pack for Parvesh-to-Rajni trip, fuel and maintenance approval testing, including genuine synthetic refill-slip files without changing the vehicle master or odometer.

Fresh Propulsive deployments now create the Haryana salary-policy establishment after verified organization facts are available, allowing the State/UT policy interface to open without inventing registrations, contribution coverage or Aadhaar data.

Organization setup now records legal constitution and planned legal-employer transitions, while governed payroll policy packs can target every Indian State and Union Territory, legal-entity type and establishment context without treating unverified rules as certified. Offer negotiation also supports managerial notice defaults and complete probation-assessment terms.

Application Settings now controls eight approved report-header layouts across compatible reports, with Banner layout C selected by default for Propulsive. Offer terms include a governed information-security and data-breach schedule, and employee attendance history uses a compact month view with monthly insights.

HR can review a branded A4 offer with governed company identity, personal-email status, salary components, notice and increment policy before applying the approved format to other employee documents.

A guarded pilot pack can validate a complete CRM-to-cash flow with linked commercial and finance records while protecting background jobs and enforcing published enterprise receipt formats.

HR can seed truthful employee lifecycle records without treating proprietor drawings as salary, while performance setup repairs only provably stale baseline roll-ups.

HR can rehearse employee entry-to-exit workflows, manage role-specific KRA and KPI plans, and use consistently sized, validated forms without exposing internal server failures.

HR can populate July and August pilot attendance and exercise leave, travel, advance and movement workflows with clearly marked synthetic evidence and a governed cleanup path.

Employees can review their approved role duties and active process ownership, while HR sees a conventional process-by-person RACI matrix.

Paid Leave and Earned Leave have been retired from Propulsive's operating policy, and prior pilot availability is reversed through auditable ledger entries.

Current employee roles can be recorded from the ERP start date without falsely treating the latest designation or manager as the employee's original joining record.

Attendance, leave and shift records now follow the 1 September 2026 operating baseline, with policy corrections retained as auditable ledger adjustments.

Thirteen effective-dated RACI processes now document responsibility and accountability across Propulsive's current HR, customer, finance, purchasing, fleet, IT and operating workflows.

The production-safe performance seed now gives every governed department a measurable, editable plan without inventing achievements or ratings.

HR can classify a training-stipend engagement as Trainee across employee records, JDs, requisitions, postings and employment history.

HR can classify each employee and hiring role against the live L1-L7 Salary Structure ladder while payroll continues to use the employee's effective Salary Revision.

HR can maintain one reusable job description for a role without forcing it into a legacy pay grade. Employee compensation continues to come from each employee's effective salary revision, including professional-service engagements that have no employee grade.

Eligible employees can submit travel allowance bills with owned receipt evidence. Each bill follows reporting-manager review, independent HR approval, and a separate Finance reimbursement record with a payment reference.

Approved attendance punch corrections now recalculate gross time, actual break deductions, personal move-out deductions, net working hours and the configured shortfall status before the corrected record reaches monthly reporting or payroll.

Attendance actions now use full-width cards. Active tea and lunch breaks show live progress against the scheduled allowance, while temporary move-outs show progress from departure to the employee's expected return time on both the attendance card and the locked return screen.

HR can now decide whether an employee may use one, two, or three active devices, choose whether a new login replaces the oldest device or is blocked, and end one or all sessions. Employee activity uses the existing business and security audit trails, with configurable retention, deletion previews and legal holds. The attendance card also reliably applies the 10/40/10 break policy to legacy shifts and locks every permitted device during an active tea or lunch break.

Salary advances now move through request, independent approval, disbursement and payroll recovery. Fleet evidence follows the reporting line, HR can publish versioned RACI ownership, selected employees can use audited inactivity controls, and attendance now locks the ERP during governed tea and lunch breaks while enforcing an eight-hour review policy.

A quotation's tax now splits the way the law expects: CGST and SGST when the site is in your own state, IGST when it is not, decided from the site on the quote and printed as separate lines on the proforma. The total is unchanged either way — only its composition. Elsewhere this release is about a quote telling you what it could not work out: a sliding wardrobe with no track chosen, a panel with no collection, a mechanism your library does not stock now say so on the results screen and on the hardware schedule, instead of quietly leaving the item out of the price.

Your staff can now raise and track support requests from their own profile, and your support team has a full desk to answer them with private notes, replies and resolution history. The Quote Engine gains wardrobes end to end: a unit library, all four door types including sliding, named internal layouts, lofts and their hardware on the schedule. Areas can carry their own charge and discount, optional supply lines come from the catalogue instead of being typed, and printed proposals no longer break a page straight after a heading.

A project is now one quote divided into areas — a kitchen, a study, a bedroom — each included or left out. It prints as a premium proposal the customer can sign, with your standard terms, a bill of quantities cabinet by cabinet, and optional appendices: drawings to scale, a complete hardware schedule and 3D views. Website content for the three sites is now edited, reviewed and released through the CMS.

A B2B cabinetry enquiry is now built from its carcass and shutter definitions and a grouped library of kitchen boxes, priced at the quote's channel level and printed as a proforma invoice. Each box can be divided into drawers and doors, given a handle, fitted from the hardware library, and seen in 3D.

HR can now invite a new joinee with just their personal email address; the joinee enters their own name and details through the secure link, and HR completes employment setup after approving them. Customer and supplier onboarding keeps approved records stable, stores uploaded evidence privately, applies stricter review controls, and supports refunds to the original payment method and recorded bank exceptions.

Customers, suppliers and software subscribers can now be invited to a secure onboarding page to confirm their company details, contacts, bank account and documents, and one organization can be a supplier, a customer and a subscriber under a single verified record. HR gets the same kind of secure page for new joiners and for existing employees whose records need completing. In both cases the person confirms their email with a one-time code, and nothing they enter reaches your records until someone on your team approves it.

A cabinet placed on a Quote Engine room plan can now use a technical definition, so its panels are calculated at the size it is actually built and the same panels reach the price, the cut list, the drawings and the SVG, DXF and PDF exports. This release also carries the owner's construction decisions for corner, drawer and top panels, and fixes a set of planning problems found while working through complete kitchen and wardrobe quotes.

Forms that hold a list of rows, such as document lines, addresses, discount tiers, salary slabs and workflow transitions, now keep every edit with the row it was made in. Before this release, an edit could be dropped without any message when you saved: after switching to another record while the form was still open, after removing a row from the middle of a list, or after moving a row up or down.

The process band on every module now follows the approved design: completed stages are a pale tint of the brand colour with a check, the current stage is filled, and upcoming stages are plain tiles with an empty circle. Module Process Flow pages show bold, clearly separated stages instead of a thin strip. On an opportunity, stages carry their real names, the band ends in a single Won / Lost stage, stages ahead are shown as upcoming, and a stage the opportunity actually moved on from shows as completed with the date it did.

Every module now has a Process Flow page that explains how its work moves from stage to stage, and an opportunity shows how far its own work has actually progressed, built from the quotations, orders, projects, surveys, deliveries and invoices saved against it rather than from its pipeline stage alone. Projects can start from ten reviewed milestone templates, with a preview of the plan against working days and holidays before anything is created. Customers now carry an explicit GST registration declaration and an individual or business identity, instead of both being guessed from whether a GSTIN happens to be recorded.

The Digital Employee ID has had a card design, a printable PDF, a scannable code and a public verification page for some time — and no way to issue one, so every employee's Workspace read "No Digital ID has been issued for you yet — ask HR to issue one" and HR had nowhere to do it. HR can now issue, reissue, suspend, reinstate and revoke a Digital ID from an employee's record, which makes the rest of it reachable for the first time. Alongside that: three of the four attendance card formats on Home carried no identity at all, and choosing a format did nothing until the page was reloaded; the calendar and the organization chart stopped short of the space they were given; and the Lead and Opportunity forms now follow the same sectioned pattern as the Employee form.

Opportunities opens on the board view, and a card on that board offered only an edit pencil — so clicking an opportunity opened the edit form, and the opportunity’s own page was reachable only from the table view, and only if you knew to switch first. The card title is now a link, so the record opens from the view that actually opens. Alongside that, three things on the record page that were visibly wrong have been corrected: the progress stages had a grey groove between them instead of meeting cleanly, the pipeline drew a dangling branch for “Lost” that the approved design does not have, and the GST panel was overlapping its own text inside the narrow side column.

The opportunity screen has been taken through the approved design one element at a time rather than in outline. It now opens with a single heading naming the record, its customer and its reference — “OPP-0142 · Asha Mehta — Kitchen renovation” — over the line of context the design shows, instead of two competing titles. Its fields sit in two labelled columns, each value in its own box, as drawn. Activity is a dated table with the person who logged each entry. The GST check sits inside the readiness card where the design puts it, rather than beside it, and the next agreed action carries the page’s one filled button.

The opportunity record page kept three of its four sections behind tabs, so opening an opportunity showed you a quarter of it — and the part it hid worst was the activity history, which sat out of sight of the readiness check a few inches away that grades whether the record has any activity at all. The page is now a single column of cards you scroll, in the order the approved design shows: the opportunity’s own details, the site surveys raised against it, then its activity. The Process Flow page has been brought to the same chrome, with the process picker where the design puts it.

Two things the owner asked for after looking at the running system. The application had been calling the same record a “deal” in some places and an “opportunity” in others, sometimes on the same screen — the record page was headed “Opportunity details” under a breadcrumb reading “Deals”. It is now called an opportunity everywhere a person can read it. Separately, thirty screens — every module overview, dashboard and command centre — carried a strip of process stages above their figures. That strip describes a process rather than reporting on any particular record, so it was grey on every one of them, and it has been taken off. It remains where it means something: on a record, showing that record’s progress, and on the module’s own Process Flow page.

Quote Engine was drawing its icons from a different icon set than the rest of the product — different shapes and weights on every button, list row and panel, on every screen. Beside it in the same menu sat the older commercial quotation screens, which were on the correct set, so the newer workspace was the one that looked out of place. Every Quote Engine icon now comes from the same set as the rest of the application. The menu has also been reduced to the Quote Engine itself: the older commercial quotation and commercial masters screens no longer appear in it.

Opening an opportunity from the deals list showed a progress band, a readiness checklist and a set of tabs, and nowhere on the screen did it say who the opportunity was for. The list row beside it showed the company and the contact; the record page showed neither. The cause was in the API: the list query asked for those names and the single-record query did not, so the page was sent two identifiers and had nothing to display. With the names arriving, the page now leads with an Opportunity details card carrying the record’s own facts, and the next agreed action moves to the side panel where it sits beside the check that grades it.

The Quote Engine’s own screens — its Command Center, quote list, calculation coverage and quote progress board — were missing the process band that every other module carries at the top of its landing and list screens, and their summary figures were plain unclickable panels. Opening Quote Engine therefore looked like arriving in an older, separate product, whatever the screens further in looked like. The band is now there, and each figure on the Command Center is a real card: it says what the number means and where it came from, and clicking it opens the records behind it.

Twelve modules had a record screen — the page showing one support case, one work order, one purchase order, one asset — and nothing in the application linked to any of them. They were built and they worked; there was simply no way to open one. The only process flow anyone could reach was the module guide page, which explains a process rather than tracking a record, so every stage there reads as not yet started and the whole band is deliberately grey. That is why the flow looked colourless: not a broken palette, but the correct rendering of the only page that could be opened. Each list now opens its record from the identifier in the row.

The CAD planning and drawing screens that arrived in 1.5.0 worked, but they were laid out like a standard record page — a heading, a row of summary tiles, then stacked notices — rather than like the drawing workspace they were designed as. This rebuilds them on the layout the design review approved: the quote’s name and status at the top with its key facts on one line, the process band beneath it, a row of sections, and then a single framed workspace holding the list of views, the drawing itself with its own toolbar, and a properties panel beside it. Nothing about the drawings, the calculation or the exports changed — only where things sit and how the screen reads.

The corporate site’s homepage lived in the website source, so changing a headline meant a developer and a rebuild. This release moves that page into the CMS: the homepage is imported as a governed draft, edited and published through the normal page workflow, and the website reads it from the published feed. Publishing a page still does not make a hidden site readable — the public feed checks that the site itself is published, not just the page.

The Quote Engine could price a kitchen but never place one. It calculated parts — a width, a height, a thickness and a quantity — with nothing to record which drawer sat in which cabinet or how high a shelf landed, so no drawing could be derived from a quote and the two were kept in step by hand. This release adds a planning workspace where cabinets and wardrobe bays are placed against measured walls, and produces the plans, elevations and sections from the same saved calculation the quote is issued from — so a drawing cannot describe a different kitchen from the one being priced. Alongside it: the HR onboarding flow, process-flow status on 22 of 23 modules, and several dropdowns that were being clipped by the panels they sat in.

The calendar that arrived in 1.3.0 showed the right work in the wrong shape: everything sat at the top of its hour, a fifteen-minute call and a three-hour installation drew the same block, two meetings in one hour covered each other up, and the panel beside the grid was usually empty. This rebuilds the workspace around a continuous time grid where an event sits at the minute it starts and is as tall as it actually lasts. There is a Day view, a small month navigator for jumping around, a list of your calendars you can switch on and off, and event details that open where you clicked instead of in a permanent side panel. Times are now shown in your organisation's timezone throughout — the toolbar said one thing and the grid did another.

The largest release so far, and the first to reach these servers since 1.1.56. Estimation & Quotation becomes Quote Engine: a standalone workspace that prices a kitchen, wardrobe or doorset and returns a cut list, a board plan and an issued revision that still adds up months later. A shared calendar shows everything dated you are meant to see, and the same calendar appears inside ten modules. The shop floor gets part labels it can print and a terminal it can scan at, and the drawings, BOMs and cut plans it works from now agree with each other about thickness. Account & Access is rebuilt around roles, so an HR Admin can grant a new starter their access without going to a Superadmin.

This number named two releases. On one line it merged the Design Engine and report-format work with the role-only access change and fixed a checkout lease and a test port race. On the other it made Reports-to save and gave documents their own recorded details. Both shipped as 1.1.48 before the lines were joined, so both are recorded here rather than one being renumbered after the fact.

Four defects in how credit notes, GST place of supply, mixed-category tax rates and draft invoices handle money. None has reached a customer — there are no invoices or credit notes on production yet.

Four confirmed defects from the pre-production audit: an edit that silently wiped vendor bank and tax details, salary changes visible to a role denied compensation access, quotation revisions that raised the price, and ESI charged to employees who are not covered.

Receivables that omitted money still owed, a CRM open-AR figure that collapsed to zero, and won deals credited to the wrong month.

Approvals invisible to the managers authorised to give them, settings screens hidden behind a key none of them use, and write buttons offered to viewers who cannot use them.

Customer receivables summed from the 50 newest invoices, a bank reconciliation that never looked at the ledger, marketing rates counting inbound replies, and three more totals counting the wrong rows.

A report that ignored its own filters, a cost-to-company lower than net pay, PF capped against the salary structure’s own setting, two CSV exports shipping database ids, and a sales funnel counting the wrong documents.

The Deals cards contradicted the Total beside them, and Deals and Contacts showed a dash for any company outside the first 200.

A leave tab that told you an employee had no leave, an attendance register with no names past employee 200, a monthly card that under-counted, and a register showing 100 of 340 employees with no way to see the rest.

Every e-invoice tile read a field that does not exist, expired e-way bills were counted in the wrong 100 rows, the leakage KPI counted resolved cases, appointment lists showed the oldest entries ever, and a failed audit-log fetch read as “nothing happened”.

Bank reconciliation reported that no journal line matched an amount whenever the entry was an old one, and four controls sat empty and unusable without saying why.

A tax invoice whose place of supply cannot be determined is refused at posting. It now warns on the draft instead, naming the two records to fix.

Earning ₹600 more could cost ₹62,493 in tax; two agreement features were unreachable because their permissions were never declared; and a dispatch tile reported zero when it had nothing to measure.

A reconciliation table that stopped at 200 lines, an account picker that lost everything past the first 200, and a vendor form still showing blank boxes for fields it cannot read.

The Proforma Invoice now prints like the Tax Invoice instead of a basic layout, and a discount bug in its figures is fixed. Employee documents are a list you add to, with a type, number, issue and expiry date and attachments per document. Compliance now sits under Accounts, Developer Tasks under SaaS Commercial, and Role Dashboards under HRMS.

The organization chart is a top-down tree instead of an indented list, with a focus view for one person and their reporting line. Search, zoom and Fit to screen actually work, the chart is navigable by keyboard, and the same chart reads as an outline on a phone.

Every employee card in the directory was labelled "Support" regardless of the roles actually assigned. Cards also carried a large empty gap, could shear a long name with no way to read it, and could show a deputation that had already ended.

An employee with a blank end date on an old job was credited with every year since — one 2015 row alone read as eleven years and eight months, under a heading that called it verified. The employee record also accepted anything at all as an IFSC code, held too few bank fields to produce a bank transfer, and recorded country, state and city as free text. The organization chart used about a sixth of the screen it was given.

Anyone who could open the employee directory received every employee’s bank account number and IFSC in full. Worse, a reporting manager approving a subordinate’s leave request, expense claim or resignation received that subordinate’s account number in the approval response — without holding any employee permission at all, and without being able to open the directory. Bank details now require a dedicated permission.

Approving a subordinate’s leave, expense claim or resignation returned that person’s entire employee record in the response — salary, PAN, Aadhaar, personal email and home address included. The previous release restricted the bank details on these screens; this removes everything else that was never needed there.

The link emailed to a new joiner is a password in all but name — anyone holding it can submit that person’s PAN, Aadhaar and bank details, with no sign-in. It was stored in readable form and travelled back inside ordinary onboarding responses, including one screen action that needs no permission at all. It is now stored scrambled and never sent anywhere.

No change to how anything behaves. The pending database update shipped in the previous release carried the same sequence number as one another workstream had already prepared, which would have stopped both from running. Renumbered before either was applied.

Generated documents could never show the company logo, never applied their fonts and carried no letterhead at all. All three are fixed, and the GST Tax Invoice, Sales Order and Payment Receipt were rebuilt against their reference designs.

Every deploy had been silently deleting every uploaded file. Uploads now live outside the application tree, the restored files are back in place, and documents render with real fonts, real icons and the dark-ink logo.

Sales, Purchase, Assets, Compliance and Order Fulfilment had no settings group at all, so their email templates and document formats were reachable only by someone who already knew the URL. Each has one now, and the 196-template email catalogue is in Application Settings.

Estimates and quotations could resolve three different renderers, which is why format changes kept appearing to be skipped. There is exactly one now, and the HR, CRM and ledger defects that had been sitting behind it are fixed.

Six releases shipped with the version number updating and nothing written down behind it. The missing entries are here, 26 test fixtures that had been shipping as release notes are gone, and a version with no release note can no longer be built.

Seven configuration screens that could only be opened by typing their URL are back in the sidebar, the Delivery Challan can be downloaded at last, and line endings are decided by the repository rather than by each developer’s machine.

Four replaced document editors that the previous release listed in the sidebar are retired again — they stay reachable by URL, as their retirement plan requires — and Report Formats moved beside the Studio it belongs with.

Every validated field now names its own problem instead of relying on a form-level banner, two Save buttons that blocked silently are fixed, and the automated test suites that had been skipped rather than passing are running again.

Simplifies RBAC role authoring, brands password recovery and exposes the next six professional accounting formats for governed Studio review.

Makes URE previews and PDFs render as print-ready documents and exposes safe typography and image-size controls in Report Format Studio.

Restores completed non-reserved Phase 1 applications to Pilot, aligns the GST feature flag and clears the remaining dead-route and mechanical UI-governance findings.

Keeps the shared desktop and mobile Work Inbox badges synchronized with the employee notification source for every role.

Completes country-aware phone capture in every discovered in-scope flow and makes the default-country configuration visible in Platform Settings.

Restores visible Phase 1 UI integrations that were present in completed branches but lost or masked in the combined Pilot candidate, with explicit residual ownership boundaries.

Recovered completed Phase 1 Asset/Fleet and Websites/CMS work that was omitted or masked during branch reconciliation, with exact Pilot comparison evidence.

Completed Phase 1 work from the handed-off branches is reconciled into one tested Pilot candidate, including restored HR/CRM forms, governed reports, command centers and settings.

The committed Phase 1 application candidate is available in Pilot for integrated acceptance testing.

Pilot now targets its isolated API consistently and safely refreshes browser application assets after deployment.

Employee photos now appear, several screens stopped claiming saves nobody made, and the build stamp says when it was built.

This is the first governed changelog entry. Earlier work has not been reconstructed or assigned artificial release dates.