Organization

This is the organization's own record: its name and profile, and the policies that apply to every project unless a project overrides them. Administrators come here to change the name, decide whether everyone must use two-factor authentication, allow AI assistants, set the defaults every project inherits and keep the statutory rules (RERA escrow share, TDS on sales, cancellation forfeiture) up to date.

Where to find it

Open the account menu in the top bar, choose Settings (see Settings), then the Organization tab. It is the first tab, so administrators land here when they open Settings. The Turn them on in Organization settings link on the AI connectors page also brings you here.

You need the View permission on Organization Settings to see the page. Without it the page shows "No access" and "You do not have permission to view organization settings. Ask your administrator." In the default roles the Administrator, Finance Lead, Project Manager, Accountant, Sales Manager, Compliance Officer, Auditor and Rehab Officer can view it; only the Administrator holds the Edit permission on Organization Settings that every change here needs. Without the Edit permission every field and toggle is disabled and the add, edit and delete buttons are hidden.

What you see

The header reads Organization with the line "Your organization's profile, security, AI connector and project defaults, tax, escrow and cancellation rules." Below it are nine cards, top to bottom.

Profile

"Shown to your team and on documents."

Field	What it means
Organization name	Required, 2 to 100 characters ("Use at least 2 characters" / "Use at most 100 characters"). Shown in the top bar and on documents.
GSTIN	Editable only while the organization has none (sign-up left it blank): "15-character GST identification number; fixed once saved". Once saved it is read-only, with the note "Fixed at sign-up."
Description	Optional, "Optional, up to 255 characters" ("Use at most 255 characters").
Invitation links expire after (hours)	How long a new user's invitation email stays valid: "1 to 720 hours (30 days)", 72 by default. Messages: "Enter a number of hours", "Whole hours only", "At least 1 hour", "At most 720 hours (30 days)".
Created	The date the organization was created.

Security policy

A line counting "N users, M without two-factor authentication.", then the toggle Require two-factor authentication for all users with the explanation "Users without it can still sign in but only to set it up; every other page is blocked until they do."

AI connectors

The link Manage connections (which opens AI connectors) and 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." It is off for a new organization.

Help assistant

The toggle Record help-assistant chats: "Questions, answers and the articles used are kept for 180 days to find gaps in the help; PAN, Aadhaar, phone numbers, emails and account numbers are masked before anything is stored. Off: nothing is stored and answers cannot be rated." It is on for a new organization.

Projects

The RERA gate and the defaults every project inherits unless it sets its own on its Settings tab. The card opens with "Under RERA a project cannot be marketed or sold before it is registered. With this on, no estimate or booking can be made on a project until its RERA registration number and date are recorded; the setup wizard still lets you skip the step and warns instead." and the toggle Require RERA registration before selling ("Applies to every project of the organization; opportunities (leads) can still be recorded."). It is on for a new organization.

Four sections follow:

• Estimate validity and unit hold: "A unit is held for a buyer from the moment their estimate is sent: no other estimate can be sent on it until this one is cancelled, expires or is booked. Estimates without a validity date expire this many days after sending (every hour a job releases expired holds). A project can set its own number of days." The Default validity box takes 1 to 365 "days from sending" (7 by default) with its own Save button. An invalid number only turns the box red; there is no message.
• Chargeable area: "Which of a unit's three areas money is worked out on. Buyers and members may differ: a Per Sqft price on a buyer's estimate multiplies the buyers' area, while a member's offer (the entitlement, the allotted units, the extra area and an allottee's purchase) is measured in the members' area. A change here reaches new projects only: every existing project keeps the area it has today, to be changed on its own Settings tab, where existing offers and estimates can be reviewed before they move." Two lists, Chargeable area for buyers and Chargeable area for members and tenants, each offering Carpet Area (Mofa), RERA Carpet Area and Super Built-up Area; Carpet Area (Mofa) is the default for both. See Unit areas and the chargeable areas.
• Carpet area offered to allottees: "On redevelopment projects, how much more carpet area (Mofa) an allottee is offered than they hold today, as a percentage; negative when the new building gives back less. Guidance only: it fills an offer that says nothing else, and every offer can be typed over. Blank = no default; a project can set its own." The Carpet area offered (Mofa) box takes -100 to 200 "% of existing" in steps of 0.5, with the placeholder "No default" and its own Save button. An invalid number only turns the box red; there is no message.
• Revenue recognition: "The revenue method and the booking event that transfers control, for every project unless it sets its own. Blank = the revenue policy of the promoter's books decides (the CA's effective-dated policy under Accounting > Revenue Recognition)." Two lists, both with the placeholder "Books' revenue policy": Revenue method (Point in time, Over time (stages achieved), Over time (cost incurred)) and Recognise revenue on (Possession offered, Possession handed over, Deemed handed over, Conveyance registered).

Errors from this card appear in one red alert under it.

Agreements & approvals

"RERA section 13 caps what may be taken before a registered agreement for sale; state sanctions and NOCs can gate selling." Advance cap before a registered agreement (percent of the consideration, 10 by default, with Save), the toggle Refuse receipts over the cap ("On: a receipt that would take a booking past the cap before a registered agreement is refused outright. Off: it is recorded with a warning.") and the toggle Require approvals before selling ("On: a project is not ready to sell until every approval type marked “required before sale” (Settings > Lookups > Approval types) has a current row on its Approvals tab. Off: a missing one is a note on the readiness card."). See Agreement for sale compliance and Approvals.

RERA escrow share

"The share of every collection the bank sweeps to the project's RERA separate account: 70% under RERA 2016. Add a new row when the regulation changes; the sweeps, the statement and the receipt warning use the rule in force on the date. A project on other terms sets its own share on its Settings tab."

A table of rules with Effective from, Escrow share and Notes, newest first. The rule that applies today carries the badge In force; a rule starting later carries Upcoming. A new organization starts with 70% from 1 May 2017.

What the rule drives: every buyer payment enters the project's collection account, and the bank sweeps it daily. The rule in force on the clearing date is the split of that sweep, recorded under RERA sweeps: that share to the project's RERA separate account, the rest to its operative account. The same figure is quoted in the warning on a receipt banked outside the collection account ("… where the bank sweeps it N% to the separate account"), is the required share on the RERA accounts statement, and heads the dashboard's RERA accounts card. A project on other terms may override it with its own RERA escrow share under Accounting on its Settings tab. See RERA accounts and the daily sweep.

TDS on sales (section 194-IA)

"What the buyer deducts on each installment once a deal's consideration (all charges excluding GST) reaches the threshold. Add a new row when the law changes; the rule in force on the demand date applies, so older demands are unaffected."

Columns Section, Effective from, Rate, Threshold ("Always" when the threshold is 0) and Notes. Each section has its own In force rule; later rules show Upcoming. A new organization starts with section 194-IA at 1% above ₹50,00,000 from 1 June 2013.

Booking cancellation rules

"What a cancellation forfeits by default and which extra charges it suggests. The organization rule applies everywhere, a project rule overrides it, and the cancellation wizard can override both for one booking. Add a new row when the policy changes; the rule in force on the cancellation date applies."

Columns Scope ("Organization" or the project's name), Effective from, Forfeiture ("10% of agreed total" or "10% of amount received"), GST (the rate, or "none") and Default charges (each charge with its amount or percentage and "+GST" where it applies, or "—" when there are none). Each scope has its own In force rule; later rules show Upcoming. A new organization starts with 10% of the agreed total, no GST, for every project.

What you can do

Save changes

In the Profile card, saves the name, description and invitation expiry. The button is greyed out until you change something. On success the message "Organization updated." appears and the name in the top bar refreshes.

• Who: anyone with the Edit permission on Organization Settings. Without it the button isn't shown.
• Blocks: another organization already using the name (case doesn't matter) shows "An organization with this name already exists." under the name field.
• What happens next: the new expiry applies to invitations sent or resent from now on; existing invitations keep the expiry they were sent with.

Require two-factor authentication for all users

Turning the toggle on opens "Require two-factor for everyone?", which says either "N user(s) has / have not set it up yet. They will be limited to their profile page until they do." or "Every active user already has two-factor authentication enabled.", with Cancel and Require two-factor.

Turning it off opens "Stop requiring two-factor?": "New users will no longer have to set up two-factor authentication." followed by "N user(s) has / have it turned on. You can leave it on for them (they can turn it off themselves) or turn it off for everyone now." or "Nobody has it turned on at the moment." The buttons are Cancel, Turn it off for everyone and Keep it for users who have it:

• Keep it for users who have it makes two-factor optional; people who use it keep it and may turn it off themselves. You see "Two-factor authentication is optional again."

• Turn it off for everyone makes it optional and also removes two-factor, with the backup codes, from every account in the organization. You see "Two-factor authentication is optional and turned off for everyone." Nobody is signed out; their next sign-in asks for the password only.

• Who: anyone with the Edit permission on Organization Settings.

• Blocks: you must have two-factor authentication on your own account first. Otherwise the card shows "Enable two-factor authentication on your own account before requiring it for everyone." with the link Set up yours in My Profile.

• What happens next: the message "Two-factor authentication is now required for everyone." appears. While the requirement is on, nobody can turn their own two-factor off (Disable two-factor on My Profile is greyed out), and a user who loses their phone and backup codes is reset by an administrator on Users. Every user without two-factor authentication sees the red banner "Your organization requires two-factor authentication. Until you set it up, most pages will refuse to load data." with a Set up two-factor authentication link on every page except My Profile, and any data they try to load answers "Your organization requires two-factor authentication. Set it up in My Profile to continue." See Two-factor sign-in.

Allow AI connectors (MCP)

Turning the toggle on opens "Allow AI connectors?": "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." with Cancel and Allow AI connectors. Turning it off saves at once.

• Who: anyone with the Edit permission on Organization Settings.
• What happens next: "AI connectors are now allowed." or "AI connectors are turned off; every connection stops at its next request." While the switch is off, the page where a user would allow an assistant to connect says "Your organization has not turned on AI connectors. An administrator can allow them under Settings > Organization." and existing connections fail at their next request. They are not revoked: they stay listed as Active on AI connectors. Once the switch is back on, an assistant that no longer works must be connected afresh from the assistant's side.

Record help-assistant chats

Saves the moment you change it.

• Who: anyone with the Edit permission on Organization Settings.
• What happens next: "Help-assistant chats are recorded again." or "Help-assistant chats are no longer recorded." While it is off, Ask NirmaanOne still answers but stores nothing, and the 👍 / 👎 under answers are replaced by Feedback off. Chats recorded earlier are kept until their 180 days are up. See Help assistant for what is masked before storage.

Require RERA registration before selling

Saves as soon as you flip the toggle; there is no confirmation.

• Who: anyone with the Edit permission on Organization Settings.
• What happens next: "Estimates and bookings now need the project's RERA registration." or "RERA registration is no longer enforced before selling." With the gate on, creating an estimate or a booking on a project without a RERA registration number and date is refused; recording opportunities is still allowed.

Save (Default validity)

Saves the number of days a sent estimate stays valid and holds its unit. The button is greyed out until the number is valid (a whole number from 1 to 365) and different from the saved value.

• Who: anyone with the Edit permission on Organization Settings.
• What happens next: "Estimates now stay valid for N days from sending." A project's own validity, set on its Settings tab, wins over this value.

Chargeable area for buyers

Choosing a value in the list saves it at once, with no confirmation.

• Who: anyone with the Edit permission on Organization Settings.
• What happens next: "Buyers are now priced on the <area> for new projects. <n> existing project(s) keep(s) the previous area; change each one under its Settings tab." or, when every project already had its own value, "Buyers are now priced on the <area> for new projects. Existing projects keep their own setting." Per Sqft prices on buyers' estimates and quotes in projects created from now on multiply this area. Existing projects do not move: each one that was inheriting is stamped with the area it had, so nothing it prices changes until someone changes the project on its Settings tab, where existing offers and estimates can be reviewed first (Change the chargeable area).

Chargeable area for members and tenants

Choosing a value in the list saves it at once, with no confirmation.

• Who: anyone with the Edit permission on Organization Settings.
• What happens next: "Members and tenants are now measured on the <area> for new projects. <n> existing project(s) keep(s) the previous area; change each one under its Settings tab." or "… Existing projects keep their own setting." Offers (entitlement, allotted units, extra area, the split) and allottees' purchase estimates in projects created from now on are measured on this area; existing projects keep theirs, as above. See Change the chargeable area.

Save (Carpet area offered (Mofa))

Saves the default uplift for offers to allottees, or clears it when the box is empty. The button is greyed out until the number is valid (-100 to 200) and different from the saved value.

• Who: anyone with the Edit permission on Organization Settings.
• What happens next: "Project defaults saved." On every redevelopment project without its own Carpet area offered (Mofa), a new offer that records the allottee's existing carpet area but names no offered area is filled in as the existing area plus this percentage. Offers already drafted keep their figures.

Revenue method / Recognise revenue on

Choosing a value in either list saves it at once, with no confirmation; choosing the placeholder "Books' revenue policy" clears it.

• Who: anyone with the Edit permission on Organization Settings.
• What happens next: "Project defaults saved." Every project without its own override now follows this method or trigger instead of its promoter's books' Revenue policy; the change applies from the next revenue run, and runs already posted keep their figures. A project can still override both on its Settings tab.

Add rule (RERA escrow share)

Opens "New escrow rule" with Escrow share (%) (0 to 100, 70 to start), Effective from (today to start) and Notes (for example "e.g. RERA 2016 section 4(2)(l)(D)"), with Cancel and Save. The pencil icon on a row (tooltip "Edit rule") opens the same dialog as "Edit escrow rule".

• Who: anyone with the Edit permission on Organization Settings. Without it the button and the row icons are hidden.
• Blocks: only one rule can start on a given date: "An escrow rule already starts on that date." A percentage outside 0 to 100 shows "Please correct the highlighted fields." (nothing is highlighted in this dialog; check the percentage). An empty percentage is saved as 0.
• What happens next: "Escrow share N% from <date> saved." Sweeps split by the rule in force on their clearing date, and the receipt warning, the RERA accounts statement and the dashboard card use the rule in force on the date concerned; sweeps already posted keep their split.

Delete rule (RERA escrow share)

The trash icon on a row (tooltip "Delete rule") opens "Delete escrow rule?": "Reports for dates covered by another rule keep using that rule. The last rule cannot be deleted; change its percentage instead." with Cancel and Delete.

• Who: anyone with the Edit permission on Organization Settings.
• Blocks: the last remaining rule: "Keep at least one escrow rule; change its percentage instead."
• What happens next: "Escrow rule deleted."

Add rule (TDS on sales)

Opens "New TDS rule" with Section (194-IA to start; letters are upper-cased; "Enter the section" when empty), Effective from (required, "Enter a date"; "The rule applies to demands dated on or after this day."), Rate in % (required, 0 to 100; 1 to start), Threshold in ₹ ("Consideration excluding GST at or above which TDS applies; 0 for always."; ₹50,00,000 to start) and Notes (for example "e.g. Finance Act 2013"), with Cancel and Save. The pencil icon on a row (tooltip "Edit 194-IA rule from <date>") opens "Edit TDS rule".

• Who: anyone with the Edit permission on Organization Settings.
• Blocks: one rule per section per start date: "A 194-IA rule already starts on <date>" (the date is written year-month-day). Number fields show "Enter a number", "Must be at least 0", "Must be at most 100" or "Use at most 2 decimal places".
• What happens next: "194-IA rule from <date> saved." Demands and demand runs dated on or after that day deduct at the new rate; demands already raised keep their figures.

Delete rule (TDS on sales)

The trash icon (tooltip "Delete 194-IA rule from <date>") opens "Delete TDS rule?": "The 194-IA rule effective <date> is removed. Demands already raised keep the figures they were raised with. The last rule of a section cannot be deleted; set its rate to 0 to stop deducting." with Cancel and Delete.

• Who: anyone with the Edit permission on Organization Settings.
• Blocks: the last rule of a section: "Keep at least one 194-IA rule; set its rate to 0 to stop deducting".
• What happens next: "TDS rule deleted."

Add rule (Booking cancellation rules)

Opens "New cancellation rule" with Scope ("Organization (every project)" or one of your projects), Effective from (today to start), Forfeiture in % (10 to start), Percent of (Agreed total (excluding GST) or Amount received), the box Charge GST on the forfeiture with GST rate (18 to start), Default charges and Notes (for example "e.g. Board resolution of March 2026"), with Cancel and Save. The pencil icon on a row opens "Edit cancellation rule".

Under Default charges, Add adds a row with "Charge name", "Amount", "or %" and a GST box, each with a remove icon. With no rows the dialog says "None. A charge is a fixed amount or a percentage of the agreed total, with or without GST; the wizard suggests it and the user can change it." Rows without a name are dropped when you save; empty numbers are saved as 0.

• Who: anyone with the Edit permission on Organization Settings. The project list in Scope needs the View permission on Projects; without it only the organization scope is offered.
• Blocks: one rule per scope per start date: "A rule for this scope already starts on that date." Other server checks show "Please correct the highlighted fields." without highlighting.
• What happens next: "Organization rule from <date> saved." (or the project's name). The cancellation wizard proposes the rule in force on the cancellation date: the project's rule if it has one, otherwise the organization's.

Delete rule (Booking cancellation rules)

The trash icon opens "Delete cancellation rule?": "Cancellations already recorded keep the figures they were posted with. The last organization-level rule cannot be deleted; set its percentage to 0 instead." with Cancel and Delete.

• Who: anyone with the Edit permission on Organization Settings.
• Blocks: the last organization-level rule: "Keep at least one organization-level rule; set its percentage to 0 to forfeit nothing."
• What happens next: "Cancellation rule deleted."

Manage connections

Opens AI connectors. Everyone who can see this page can follow the link.

Statuses

Rule rows in the three rule cards show:

Badge	Meaning
In force	The rule that applies today: the latest one starting on or before today, per section (TDS) or per scope (cancellation).
Upcoming	A rule whose start date is still in the future. It takes over on that date.

A rule with neither badge has been superseded by a later one and still governs the dates it covered.

Things to know

• Add a rule, don't edit the old one, when the law changes. Sweeps, the RERA accounts statement, demands and cancellations use the rule in force on their own date (see Effective-dated rules). A new row with the new figure and its effective date keeps every older document consistent with the rule that applied when it was raised; editing the old row would rewrite history.
• The last rule can never be deleted. Each card must keep at least one rule (per section for TDS, at organization level for cancellation), so there is always a rule to apply. To stop a deduction or forfeiture, set the rate to 0 instead.
• Four changes save without asking. Require RERA registration before selling, Area basis, Revenue method and Recognise revenue on save the moment you change them, although they affect every project without its own override. Check before you click.
• The two-factor requirement starts with you. You cannot require two-factor authentication for everyone until your own account has it, so an administrator can never lock themselves out of their own policy. Set it up on My Profile first.
• Turning AI connectors off does not revoke connections. They fail at their next request but stay listed as Active; once the switch is back on, an assistant that no longer works has to be connected afresh. To end a connection for good, revoke it on AI connectors.
• The user counts include everyone. "N users" counts active, inactive and invited users; "M without two-factor authentication" counts active accounts without it, including people who have been invited but not yet joined.
• Only section 194-IA is applied. The TDS card lets you record other sections, but demands, demand runs and termsheets deduct only under 194-IA.
• Projects inherit, and can override, most of these settings. The estimate validity, the area basis, the carpet area offered, the revenue method and trigger, and the RERA escrow share can each be set per project on its Settings tab, where the hint under each field shows the value in force and where it comes from; the cancellation rule is set per project with a rule whose Scope is the project. The project's value wins, and clearing it goes back to the organization's. For the revenue method and trigger there is a third level: with nothing set here or on the project, the promoter's books' revenue policy decides.
• GSTIN can be added once, never changed. An organization that signed up without one enters it here; after it is saved (or when it was given at sign-up) it is fixed: an attempt to change it answers "The GSTIN is fixed once recorded; contact support to correct it." A GSTIN already used by another organization is refused: "An organization with this GSTIN already exists".
• There is no History button on this page. Changes to the organization record are still written to the Audit log, which needs the View permission on Audit Trail.

Related

• Settings
• Users
• AI connectors
• Ask NirmaanOne (help assistant)
• Help assistant
• My Profile
• Two-factor sign-in
• Edit project
• Project settings
• Revenue policy
• RERA accounts
• RERA sweeps
• RERA accounts and the daily sweep
• Demand
• Cancel booking
• Audit log
• Set the organization's profile and project defaults
• Effective-dated rules
• Unit areas and the chargeable areas
• Change the chargeable area
• Change the chargeable area (how-to)
• Project readiness and the RERA gate
• Pages refuse to load data: your organization requires two-factor authentication