AI connectors
How an AI assistant such as Claude or ChatGPT connects to NirmaanOne, acts as one user within that user's role, what it can and cannot do, and how connections are watched and stopped.
AI connectors
An AI connector is a link between an AI assistant (Claude, ChatGPT or any other assistant that supports custom connectors) and NirmaanOne. Once connected, the assistant can look up records and make everyday changes on a user's behalf, as if that user had done it in the app. Each connection belongs to exactly one user and works inside that user's organization only.
How it works in NirmaanOne
Turning connectors on
Connectors are off for a new organization. An administrator turns them on under Organization with the switch Allow AI connectors (MCP) (it needs the Edit permission on Organization Settings). Turning the switch on asks for confirmation, because from then on every user can connect an assistant. Turning it off stops every existing connection at its next request; the connections are not deleted, so the assistant simply gets a refusal until the switch is on again.
Connecting
Every signed-in user can open AI connectors (the Settings tab is shown to everyone). The page shows the MCP server URL to paste into the assistant as a custom connector. The assistant then sends the user to the Connect an app page, which asks them to sign in with their usual email, password and second factor, shows who is asking, and offers Allow or Deny. Choosing Allow creates the connection.
Three things must be true for Allow to work: the organization switch is on, the user can sign in, and, when the organization requires two-factor authentication, the user has set it up.
The connection acts as the user
A connection is not a separate account. Every request the assistant makes runs as the connected user, with exactly the permissions of that user's role at that moment, and sees only that organization's records. So:
- the assistant is offered only the actions the user's role allows; anything else is simply not available to it, and a request that the role does not permit is refused as a missing permission, just as it would be in the app;
- a change to the user's role reaches the assistant at its next request;
- every change the assistant makes is recorded in the audit trail under the user's name, shown as "<name> via AI connector" (see Audit trail and record history).
What an assistant can do
Reads across the business: projects and their structure, unit inventory, parking slots, tenants and allottees, contacts, opportunities, estimates, bookings, demands, receipts, tasks, the user's own notifications, the dashboard figures, the organization's lookups, document templates, letterheads and generated documents.
Everyday changes: create and update opportunities, assign them, mark them lost and reopen them, log activities, create, update and complete tasks, create and update draft document templates, preview a document against a real record, and generate a document from a published template.
It can never move money, record or clear a payment, issue a demand, approve anything, cancel a booking, publish a template or send email. For those the assistant points the user to the app.
Skills. Next to the connection, NirmaanOne offers skills: small folders of instructions an assistant reads so it works the NirmaanOne way. The first, nirmaanone-documents, teaches it to turn a user's own letter, form, PDF, Excel sheet or Word file into a document template with merge fields and if/else wording, to preview it against real records (one per case) and to leave publishing to the user. Download it under AI connectors; see Draft a document template with an AI assistant. The assistant only ever describes what NirmaanOne shows and does; it does not talk about how NirmaanOne is built.
Statuses and what stops a connection
A connection is Active, Revoked (with the date and who did it) or Expired. It stops working when:
- the user disconnects it (Disconnect on their own card) or an administrator revokes it (Revoke on All connections in your organization, which needs the Edit permission on Organization Settings);
- the assistant itself gives the connection up;
- the assistant presents a renewal token that was already used, which is treated as a sign that a copy of the token has leaked; the connection is revoked at once;
- it goes unused for 30 days: each connection carries a renewal token valid for 30 days, replaced by a fresh one every time the assistant renews its working token, so an assistant in regular use never expires;
- the user is deactivated;
- the user changes or resets their password, uses Sign out everywhere on My Profile, or has their two-factor authentication reset by an administrator (connections made before that moment stop; the user connects again afterwards). Signing out of one browser does not stop a connection;
- the user's email is still not verified 30 days after the account was created (until the email is verified);
- the organization switch is turned off.
A short-lived working token (one hour) is renewed silently by the assistant; users never see it.
Watching what a connection did
Each row's Activity opens the list of every request the assistant made: the time, the tool it used, the outcome (Success or Error), the error code and how long it took, with the arguments on hover. Administrators (with the View permission on Organization Settings) see every user's connections; everyone sees their own. Revoking a connection keeps its activity on record.
Example
Priya is a Sales Executive at Shree Siddhi Developers. Her administrator has turned on Allow AI connectors (MCP). Priya adds the server URL to Claude, signs in on the consent page and chooses Allow. Her connection appears under Your connections as Active.
- She asks Claude which 2 BHK units are still available in Tower B of Sai Darshan. Her role has the View permission on Towers, Floors & Units, so Claude reads the inventory and answers.
- She asks Claude to log yesterday's site visit on the Mehta opportunity with a follow-up next Tuesday. Her role has the Edit permission on Opportunities, so the activity is recorded. In the opportunity's History the entry reads "Priya Shah via AI connector".
- She asks Claude to raise the next demand on the Mehta booking. There is no such action for an assistant, so Claude tells her to do it in the app.
- She asks Claude to approve an estimate. Approval is never offered to assistants, whatever the role, so the answer is the same.
Three months later Priya leaves. The administrator deactivates her user; her connection stops at its next request. Even before that, the administrator could have chosen Revoke on her row under All connections in your organization ("Revoke this connection?": the assistant "stops working at its next request. Its activity stays on record.").
Where you see it
- AI connectors: the server URL, your connections, every connection in the organization, Activity, Disconnect and Revoke.
- Organization: the Allow AI connectors (MCP) switch.
- Connect an app: the consent page the assistant sends you to.
- Audit log and the History panel: changes made through an assistant, with AI Connector as the actor kind.
- Users: deactivating a user also stops their connections.
Related
Related
- AI connectorsScreen
Connect Claude, ChatGPT or another AI assistant to NirmaanOne so it can act as you, see what your connections have done, and disconnect them; administrators see and revoke everyone's.
- Draft a document template with an AI assistantHow-to
Give Claude or ChatGPT your own letter, form, PDF, Excel sheet or Word file as a reference, let it draft the template in NirmaanOne with merge fields and if/else wording, check the previews it shows, then preview and publish the draft yourself in Settings > Documents.
- OrganizationScreen
Your organization's profile and policies: name and invitation expiry, the two-factor requirement, the AI connectors switch, the help-assistant recording switch, the project defaults every project inherits (RERA gate, estimate validity, the two chargeable areas, carpet area offered, revenue method and trigger) and the effective-dated rules: the RERA escrow share that splits every sweep of a project's collection account, TDS on sales and booking cancellation.
- Connect an app (<app> wants to connect to NirmaanOne)Screen
The consent page an AI assistant sends you to when it asks to work in NirmaanOne on your behalf: see what it will be able to do, then allow or deny it.
- Audit logScreen
The organization-wide change log: every create, change and delete, every sign-in (including refused ones), sign-out and downloaded file, with who did it, when, from where and what changed.
- History panelScreen
See who changed a record, what they changed and when, including the record's lines, newest first, and jump to the full audit log.
- UsersScreen
The people in your organization: invite new users, change their role, deactivate or reactivate them, reset a lost two-factor authentication, and resend or revoke pending invitations.
- Two-factor sign-inScreen
Turn on two-factor authentication with an authenticator app, sign in with a 6-digit code or a backup code, manage your backup codes, and what happens when your organization requires it.
- Roles and permissionsConcept
What a permission is (a module plus an action), how roles bundle permissions, the twelve default roles and what each is meant for, the one-role-per-user rule, and when a change reaches a signed-in user.
- Audit trail and record historyConcept
What an audit entry records (who changed what, when, from where, with before and after values), how entries group into a record's history and a project's history, and who may read them.
- User accounts: invitations, status and sign-inConcept
How a person gets an account (by invitation), the four user statuses and how they are derived, how long an invitation link lives, what happens at sign-in with and without two-factor authentication, how long a session lasts, and what deactivation does.