NirmaanOne Help
How-toReviewed 2026-09-29

Turn on AI connectors and connect an assistant

An administrator allows AI connectors for the organization; each user then adds NirmaanOne to Claude, ChatGPT or another MCP client with the server URL, allows the connection, and can review or disconnect it later.

Turn on AI connectors and connect an assistant

An AI assistant such as Claude or ChatGPT can work in NirmaanOne for you: find records, answer questions about your projects and make everyday changes. It connects as you, with your role's permissions, inside your organization only. An administrator first allows AI connectors for the whole organization; after that, each person connects their own assistant.

Before you start

  • Allowing connectors needs the Edit permission on Organization Settings. In the default roles only the Administrator has it. It is off for a new organization.
  • Connecting an assistant needs no permission of its own: everyone signed in sees the AI connectors tab under Settings. What the assistant may then do is exactly what your role permits.
  • If your organization requires two-factor authentication, you must have it set up on your own account before an assistant can connect. See Set up two-factor authentication and require it for everyone.
  • You need an assistant that supports custom connectors (MCP), such as Claude or ChatGPT.

Steps

  1. Administrator: open the account menu in the top bar, choose Settings, then the Organization tab (Organization). Find the AI connectors card with the toggle Allow AI connectors (MCP): "Users can connect Claude, ChatGPT or other MCP clients. Each connection acts as that user, with their roles' permissions, inside this organization only. Turning this off stops every connection at its next request."
  2. Switch on Allow AI connectors (MCP). The dialog "Allow AI connectors?" says "Every user can then connect an AI assistant that reads and changes records as them, within their roles' permissions. It cannot move money, issue demands, approve, cancel bookings, publish templates or send email. You can see and revoke every connection under Settings > AI connectors."
  3. Click Allow AI connectors. You see "AI connectors are now allowed."
  4. Each user: open the account menu, choose Settings, then the AI connectors tab (AI connectors). The card Connect an AI assistant reads "Add NirmaanOne to your assistant as a custom connector with this server URL." and shows the MCP server URL. If the card instead warns "AI connectors are turned off for your organization, so new connections cannot be made and existing ones stop working.", an administrator has to do steps 1 to 3 first.
  5. Click Copy next to MCP server URL. The button reads Copied for a moment.
  6. In Claude, open Settings > Connectors > Add custom connector, paste the URL and choose Connect. ChatGPT and other MCP clients work the same way. Your browser opens NirmaanOne; if you aren't signed in, sign in first (with your two-factor code, if you use one) and you come straight back. The Connect an app page reads "<App> wants to connect to NirmaanOne" and "Signed in as <email> in <organization>."
  7. Read the box "If you allow it:" (it acts as you with your roles' permissions, only sees your organization's data, "cannot move money, issue demands, approve, cancel bookings, publish templates or send email") and check that the site under "You will return to" is the assistant you started from. Click Allow. The page reads "Returning to the app…" and you are back in the assistant, which now lists NirmaanOne as a connector.
  8. Back in NirmaanOne, open Settings > AI connectors. Under Your connections the assistant has a row with Status Active. Once it has done something, click the list icon on the row (tooltip "Activity"): the dialog "Activity of <app>" lists each call with its Time, Tool, Outcome (Success or Error), Error code and Duration.

What happens next

  • Everything the assistant does is recorded under your name, shown as "<your name> via AI connector" in a record's History panel and in the Audit log, so colleagues can tell its changes from yours.
  • It stays within your permissions. If your role changes, the assistant's powers change with it.
  • To stop it, click the ban icon on its row under Your connections (tooltip "Disconnect") and confirm Disconnect in "Disconnect this assistant?". You see "<app> disconnected." and the row becomes Revoked. To use it again, connect afresh from the assistant.
  • Administrators see every connection. With the View permission on Organization Settings, the card All connections in your organization lists everyone's connections with their Activity; with the Edit permission, Revoke ends one ("Revoke this connection?").
  • A connection ends by itself after 30 days without being renewed by the assistant (Expired), and stops working when its user is deactivated, signs out everywhere or changes their password.
  • Turning the organization switch off stops every connection at its next request ("AI connectors are turned off; every connection stops at its next request."), but doesn't revoke them: they stay listed as Active. While the switch is off the assistant is told "AI connectors are turned off for this organization"; if it has dropped the connection by the time the switch is back on, connect it afresh.
  • To let Claude run tools without asking each time, follow Stop Claude asking before every tool on the AI connectors page; "Whatever you allow, the assistant can only do what your NirmaanOne role permits."

If something goes wrong

  • The consent page shows "Your organization has not turned on AI connectors. An administrator can allow them under Settings > Organization." and Allow is greyed out: steps 1 to 3 haven't been done, or the switch was turned off. See Connecting an AI app is refused.
  • The consent page shows "Set up two-factor authentication first": your organization requires two-factor authentication and yours is off. Click Set up two-factor authentication, set it up, then start again from the assistant. See Pages refuse to load data: your organization requires two-factor authentication.
  • The consent page shows "This connection request is not valid": the assistant isn't registered with NirmaanOne or asked to return to an address it didn't register. Start the connection again from the assistant. See Connecting an AI app is refused.
  • The toggle Allow AI connectors (MCP) is greyed out: you lack the Edit permission on Organization Settings. See No access or no permission.
  • In All connections in your organization, Revoke is greyed out with "Revoking another user's connection needs permission to update organization settings.": ask someone with the Edit permission on Organization Settings.

Related

  • 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.

  • 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.

  • 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.

  • My ProfileScreen

    Your own account: see your email, organization and roles, change your name and phone, change your password, turn two-factor authentication on or off, and sign out everywhere.

  • 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.

  • 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.

  • Set up two-factor authentication and require it for everyoneHow-to

    Turn on two-factor authentication for your own account with an authenticator app on My Profile, save your backup codes, sign in with a code, and then, as an administrator, require it for every user of the organization.

  • Change a user's roles, or deactivate a userHow-to

    Give a user a different role from Settings > Users, or deactivate someone who has left so they are signed out everywhere and can't sign in, and reactivate them if they come back.

  • AI connectorsConcept

    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.

  • Connecting an AI app is refused: connectors are off, 2FA is missing or the request is invalidTroubleshooting

    The consent page will not let you allow an AI assistant, an existing connection has stopped working, or the Revoke icon is greyed out: what each message means and who can fix it.

  • Pages refuse to load data: your organization requires two-factor authenticationTroubleshooting

    A red banner says most pages will refuse to load data, dashboard sections fail and every list shows the same message: the organization now requires two-factor authentication and your account has not set it up yet.

  • "No access" or "You do not have permission": your role lacks a permissionTroubleshooting

    Every screen, button and picker is gated by a permission on a module; your role decides which you hold, so a missing one shows as a No access card, a refused action, a greyed-out button with a hover reason, or a picker that explains which permission it needs.