NirmaanOne Help
How-toReviewed 2026-09-29

List amenities, project-wide or per tower

Record what the new project provides: amenities shared by everyone (clubhouse, gym) listed once for the project, and amenities each tower has (refuge unit, society office) listed once per tower, drawing on the organization's Amenities lookup.

List amenities, project-wide or per tower

Amenities are what the new project provides. Some are shared by everyone, such as a clubhouse or a swimming pool, and are listed once for the whole project. Others belong to a tower, such as a refuge unit or a society office, and are listed once on each tower that has them. An amenity is listed in one of the two ways, never both, so it is never counted twice.

The kinds of amenity (the names you pick from) are an organization-wide list under Settings > Lookups; the project records where each one is, how many, and how large.

Before you start

  • You need the Edit permission on Projects to add, change or remove a project's amenities. In the default roles that is the Administrator, the Project Manager and the Compliance Officer. Without it the tab is read-only and no buttons are shown.
  • Picking an amenity needs the View permission on Lookups; without it the panel warns "Listing amenities needs the Lookups permission."
  • Picking a tower needs the View permission on Towers, Floors & Units; without it the Tower field is greyed out with "Picking a tower needs the Structure permission." and the per-tower card reads "Tower names need the Structure permission; rows are still listed."
  • For per-tower amenities, the towers must exist on the Structure tab.
  • To add a new kind of amenity you need the Create permission on Lookups (in the default roles the Administrator, Finance Lead, Project Manager, Sales Manager and Rehab Officer).

Steps

  1. If the amenity isn't a kind your organization knows yet (say, "Yoga deck"), add it first. Open the account menu, choose Settings, then the Lookups tab, and the Amenities list ("Society and project amenities, grouped by category."). Click New amenity, enter the Name (the Code is made from it), a Category if you group amenities ("Optional; groups amenities in pickers"), and click Add amenity. You see “"<name>" added.” The kind is offered in every project's picker at once. A new organization starts with 13 kinds, so you can usually skip this step.

  2. Open the project and choose the Amenities tab. You see the Amenities page: the card Project-wide amenities ("Shared by everyone in the project: clubhouse, swimming pool, gym… An amenity listed here cannot also be listed per tower.") and, below it, Per-tower amenities ("Provided on each tower that has them: refuge unit, society office, tower lobby… Add the same amenity once per tower.") with one box per tower, "Tower <name>". While nothing is listed the cards read "Nothing project-wide yet" and "Nothing listed for this tower."

  3. To list something the whole project shares, click Add amenity on Project-wide amenities. The panel Add amenity slides in with Scope already set to Project-wide (shared by everyone).

  4. Fill in the panel and click Add amenity at the bottom:

    • Amenity: required, from the lookup, shown as "<name> (<category>)". Nothing picked: "Choose an amenity". The hint reminds you to "Add new kinds under Settings → Lookups → Amenities."
    • Scope: leave it on Project-wide (shared by everyone) (hint "An amenity is listed either once for the whole project or once per tower, never both.").
    • Quantity (a whole number), Area in sqft, Location (placeholder "e.g. Podium level") and Notes: all optional.

    You see "<amenity> added project-wide." The row shows the name, its category badge and "× <quantity> · <area> · <location> · <notes>".

  5. To list something a tower has, click Add on a tower on Per-tower amenities, or Add inside a tower's box to start with that tower chosen. The panel opens with Scope set to Per tower and a Tower field (hint "Add the same amenity again for each tower that has it."). Add on a tower is greyed out, with no reason on hover, while the project has no towers; the card then reads "No towers yet" and "Add towers under Structure, then list what each tower provides."

  6. Pick the Amenity and the Tower (nothing picked: "Pick the tower"; the placeholder reads "No towers yet" when there are none), fill in Quantity, Area, Location (placeholder "e.g. Refuge floor 7") and Notes as useful, and click Add amenity. You see "<amenity> added on tower <name>." and the row appears in that tower's box. Repeat for every tower that has the amenity: one row per tower.

To correct a row, click its pencil (hover "Edit <amenity>"), change the fields and click Save; you see "<amenity> updated project-wide." or "<amenity> updated on tower <name>." To take one off, click its bin (hover "Remove <amenity>"), read "Remove <amenity>?" ("It is removed from tower <name> only." or "It is removed from the project.") and click Remove; you see "<amenity> removed."

What happens next

  • The Amenities card on the setup wizard's Amenities, parking, stages & pricing step counts the rows ("<n> recorded"), and the step counts as done once any amenity, parking area, stage or pricing plan exists. See Walk through the project setup wizard.
  • Amenities are a record of what the project provides. They don't price anything and aren't attached to units; a Common unit that houses an amenity (a gym on a floor, say) is set on the unit itself under Structure, which uses the same lookup.
  • To move an amenity from project-wide to per tower (or back), remove its existing row first; the app refuses to list the same amenity both ways.

If something goes wrong

  • "This amenity is already listed for the society." under Amenity: the amenity is already listed at that place (project-wide, or on that tower). The message says "society" but means the project or the tower. Edit the existing row instead. See Amenity already listed (trouble.admin.already-exists).
  • "This amenity is listed per tower; remove those rows before listing it project-wide" or "This amenity is listed project-wide; remove that row before listing it per tower" at the top of the panel: remove the rows in the other scope first. See Amenity listed in the other scope (trouble.projects.amenity-listed-in-other-scope).
  • Add on a tower is greyed out and the card reads "No towers yet": the project has no towers, so there is nothing to list a tower amenity on. Add towers on the Structure tab first; project-wide amenities can be listed meanwhile.
  • "That tower does not belong to this project.": the tower was removed while the panel was open. Close the panel and pick again.
  • No Add amenity button, or "You do not have permission to view project amenities. Ask your administrator.": your role lacks the Edit (or View) permission on Projects. See No permission (trouble.admin.no-access).

Related

  • AmenitiesScreen

    List what the new project provides, either once for the whole project (clubhouse, pool) or on particular towers (refuge unit, society office).

  • LookupsScreen

    The dropdown lists every form draws on: contact types, lead sources, activity types, company types, bank account purposes, parking types, amenities, unit types and unit configurations.

  • StructureScreen

    Build and maintain a project's towers (wings), floors and units, generate them in bulk, and see every unit's status and designation at a glance.

  • Project setup wizardScreen

    Set up a project step by step, from the land and RERA details and bank accounts to towers, society, members, offers, amenities, parking, stages and pricing; each step saves as you go.

  • Walk through the project setup wizardHow-to

    Take a new project through the nine setup steps in order: basics, land and RERA, promoter and bank accounts, towers and units, society, members, offers, extras, and review, saving as you go and skipping what can wait.

  • Maintain a dropdown listHow-to

    Add, rename, reorder, retire or delete the values in your organization's dropdown lists (contact types, lead sources, activity types, company types, bank account purposes, parking types, amenities, unit types and unit configurations) under Settings > Lookups.

  • "Already exists" or "listed twice": the name, code, number or line must be uniqueTroubleshooting

    Names, codes and numbers are unique within their scope (the organization, a project, a tower, a set of books) so that records can be told apart, and a line can appear once on a plan, offer or account; rename, reuse the existing record, or remove the duplicate line.

  • Amenity refused: it is already listed project-wide, or already listed per towerTroubleshooting

    An amenity is listed either once for the whole project or once on each tower that has it, never both; adding it in the other scope, or moving a row across scopes, is refused until the rows in the first scope are removed.

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