The mobile installer
Records the visit, hardware movement and evidence against the correct client location.
Explore this roleCoordinate repeatable visits across customer premises while keeping each location’s work, costs, evidence and closure status distinct.
Bengaluru · Retail client premises
Demonstration project · Work in progress
Prompt ideas require a connected assistant and permitted access. Review proposed changes before saving.
Screens captured from NIYAM on 9 September 2026. Names, amounts and projects are fictional. Site photos inside the demo are AI illustrations.
For access-control, CCTV, signage and other installation businesses coordinating mobile teams across repeated customer-premises jobs.
Records the visit, hardware movement and evidence against the correct client location.
Explore this roleReviews unfinished visits, missing evidence, field costs and responsible follow-up across locations.
Explore this roleReceives selected reviewed information for its assigned work while internal costs remain private.
Explore this roleSelected progress and reports keep your client informed. Supplier bills and internal expenses stay with your team.
How sharing works
Connect assistance to your site context. Check the records, review the proposal and confirm the work you want saved.
Explore connecting ChatGPT to permitted NIYAM workflows through MCP.
ChatGPT connection guideConnect supported NIYAM tools for scoped work. Check the source, review the action and verify its result.
Codex connection guideConfigured bill extraction and report drafts support review. General internal-agent actions are not yet qualified.
See bill reviewCore site work has a complete manual path. New integrations are agreed by scope.
How MCP connects the toolsNIYAM coordinates installation records. It does not monitor devices or surveillance feeds, operate access systems, optimise technician routes, verify security performance or certify testing and client acceptance.
Review access and controlsYes. Create each client location with consistent milestone and task naming, then assign its responsible crew. The Metro Retail example keeps Koramangala and Indiranagar evidence and open work identifiable.
Site assignment, permissions and location-specific records keep the operational context separate. Review access before inviting a client or sharing a report.
No. NIYAM records installation work and review evidence. It does not receive surveillance feeds, operate access systems or show live device health without a separately verified integration.
Metro Retail records 38 door kits received and 26 used, leaving 12 recorded for physical verification. The team remains responsible for actual count, condition and suitability.
No. Client access contains selected shared site information. Travel expenses, supplier bills, reimbursements and internal commercial records remain in authorised team views.
Open tasks, missing evidence and responsible review remain visible. The Indiranagar location keeps its door-alignment follow-up open until authorised people review the supporting record and decide on acceptance.
Add the current plan, bring in your team and record the next day’s work. For an existing project, agree opening stock and balances before you carry them forward.
Plan your first site