Owner
Checks priorities across the sites they can access and decides what needs attention.
Which site decisions need me today?Explore the role
Ask about the day’s work, inspect the source and review a proposed next step with your NIYAM access.
Start with one workflow. Use your own access. Review the result.
Assisted setup · Confirm the supported workflow for your account before relying on it. The examples below explain the review process; they are not a provider recording.
Actual NIYAM screens
Fictional project · Example prompts
Check your NIYAM access and the ChatGPT workspace’s plugin policy.
With assisted setup, add the NIYAM MCP connection and sign in to the intended workspace.
Begin with a small read-only grant. Check the answer against a source record.
Enable the agreed actions, review the exact proposal and confirm only the work you want saved.
NIYAM’s public MCP endpoint uses Streamable HTTP:
https://mcp.niyam.app/mcpIn eligible ChatGPT workspaces, follow the current plugin/developer-mode connection flow. Workspace policy can restrict this option. A separately built OpenAI API integration is a different setup.
Keep private connection credentials out of prompts, shared screenshots and client-side code.
OpenAI connection guidanceDocumentation checked 8 September 2026. Provider settings and eligibility can change.
Each person uses their own identity. The assistant’s access follows their membership, role, site access and connection grant.
Checks priorities across the sites they can access and decides what needs attention.
Which site decisions need me today?Explore the role
Works from assigned sites and prepares a task, progress record or attendance update.
Prepare today’s update for my site.Explore the role
Reviews bills, duplicates and payment evidence before operational money records change.
Which bills need review, and what is missing?Explore the role
Receives selected progress and reports through the client view. Internal records stay with the team.
Review the progress shared with me.Explore the role
The client example is the shared NIYAM client view. It does not promise a client MCP connection or access to internal records.
Use an active NIYAM membership with AI Assistance enabled and a small grant for the agreed tools.
Access and controlsReview the exact site, values and effect of each sensitive proposal. Check the saved result before moving on.
How MCP worksConfirm MCP inclusion in your NIYAM agreement and the provider plan separately. API usage and custom integration work can carry separate charges.
Review plansReads use the permitted records. Sensitive actions use a prepared proposal and confirmation. Review the exact site, values and downstream effect before you approve.
Each person connects with their own identity. NIYAM checks membership, role, site access and the connection’s tool grant. Team rollout and provider availability depend on your workspace policy.
Leaving a proposal unconfirmed does not save the proposed operational change. If a save response is uncertain, check the record or recover the existing request before creating another one. Reconnect expired or revoked access as appropriate.
Check your NIYAM agreement for MCP access and your provider’s plan for the assistant. A ChatGPT or Codex subscription and separately billed API usage are different products. New integrations are scoped separately.
Yes. Sites, tasks, materials, money and reviewed reports have their own NIYAM screens. Connected assistance is an additional way to use supported work, subject to setup and permissions.
The screenshots are actual NIYAM screens with fictional project data. Example prompts explain the intended workflow. They are not recordings of a provider conversation or proof that every provider supports every action.
Agree the workflow and access, connect with support, then check the result together.