Roles and permissions
Supported access follows the workspace role, site assignment and client scope on the server and in navigation.
Set up sites, run today’s work, track people, materials and money, then share clear progress from one simple workspace.

NIYAM begins with the minimum needed to run a real site. Optional business, site and team detail stays out of the way until it is useful.
Start with the site name and location. Add dates, budget, client and milestones only when they help.
Give app users the right access, assign them to sites and keep site workers separate for daily attendance.
Open the work that needs attention, complete the next action and add more control as the business grows.

See site identity, progress, attention, milestones and people first. Tasks, attendance, materials, money, reports, photos and documents remain available as contextual links.
The team records only what is incomplete, using focused actions for progress, labour, materials, photos and issues before reviewing the DPR.

Each area has a focused working surface and uses the existing approvals, records and permissions—without turning NIYAM into payroll, procurement ERP or accounting software.

Use the responsive portal from site or office. The Expo field app separately supports focused workflows and a bounded offline queue for specifically supported actions.




Curated reference screens show the intended responsive product experience. Native Expo behavior is qualified separately.
Build a report manually from supported progress, photos, milestones and finance summary, approve it when required and create a controlled client view.


Open an area to see the practical capability list. Start with the work you need now; the same workspace keeps the other controls ready for later.
A resumable first run, focused role Home, compact Site Home and simple milestones help the team begin without a heavy rollout.
Progress, labour, material activity, photos and issues come together in one reviewable daily path instead of an oversized form.
App users and site workers stay distinct, while the daily roster keeps Present, Absent and Half day actions easy to understand.
Request what the site needs, send it for a decision, receive approved quantities and record usage against canonical stock.
Capture expenses manually, review evidence and keep vendors, approvals and supported payment activity beside the related site context.
Build reports manually, preview selected information and give clients a project-safe view without opening internal controls.
Roles, site scope, client boundaries, recorded decisions and private evidence remain part of the canonical product—not a separate Starter permission system.
Supported access follows the workspace role, site assignment and client scope on the server and in navigation.
Photos and documents stay with supported site, task, expense, DPR and report workflows.
Find permitted records, act on short notifications and reach contextual support from the same workspace.
The field app queues specifically supported actions and shows pending, synced, failed and conflict states honestly.

Manual expense capture and report creation remain available. When configured, AI can prepare supported bill fields, possible duplicate signals or draft report copy for an authorised person to review.
Compare current site, user, client, storage and reporting limits from the live pricing contract. Optional assistance remains visible without becoming a requirement.
NIYAM is intentionally clear about what the Starter experience does, where people remain responsible and what the product does not replace.
Yes. NIYAM is built first for owner-run and small-to-mid-size teams. You can start with one site and a small team, then use more controls only when they become useful.
The frequent workflows use focused pages, familiar construction language and one clear next action. NIYAM still expects each business to confirm its roles, approval responsibilities and working process.
Yes. The portal is responsive and the Expo field app supports focused operational workflows. Only specifically supported mobile actions use the bounded offline queue; the entire product is not presented as offline.
No. Attendance supports site supervision, Materials provides lightweight request and stock control, and Finance Inbox organises operational money work. NIYAM does not claim payroll, full accounting, RFQ, purchase-order or GRN systems.
No. Manual expense capture, report creation, review and approval remain complete. When configured, AI can prepare supported bill fields or report copy for an authorised person to review.
Clients see only explicitly shared Project, Reports and Messages information within their assignment. Internal workforce, vendor, approval and administration controls remain outside the client view.
Add the site, invite the team or continue solo, and let NIYAM keep the next useful action clear as the business grows.