NirmaanOne Help
TroubleshootingReviewed 2026-09-29

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

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.

Messages this explains

  • “This amenity is listed per tower; remove those rows before listing it project-wide”
  • “This amenity is listed project-wide; remove that row before listing it per tower”
  • “An amenity is listed either once for the whole project or once per tower, never both.”

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

You try to add an amenity on the project's Amenities tab, or change a row's Scope, and the panel refuses because the same amenity is already listed in the other scope.

What you see

In the Add amenity or Edit <amenity> panel, when you click Add amenity or Save, a red banner at the top of the panel reads one of:

  • "This amenity is listed per tower; remove those rows before listing it project-wide", when you choose Project-wide (shared by everyone) for an amenity that some tower already lists.
  • "This amenity is listed project-wide; remove that row before listing it per tower", when you choose Per tower for an amenity that is already on the Project-wide amenities card.

The Scope field's own hint states the rule: "An amenity is listed either once for the whole project or once per tower, never both."

A different message, "This amenity is already listed for the society.", means the amenity is already listed at that very place (project-wide, or on that same tower); see Already exists.

Why it happens

An amenity's scope says who it serves. A clubhouse or swimming pool is shared by the whole project and is listed once; a refuge unit or society office belongs to each tower that has it and is listed once per tower. Listing the same amenity in both ways would make the project's amenity schedule double-count it (in brochures, RERA disclosures and the setup review), so the app keeps the two scopes mutually exclusive: an amenity is either project-wide or per tower, and a row cannot be moved from one scope to the other while rows remain in the first.

How to fix it

Everything below needs the Edit permission on Projects; without it the icons are not shown.

  1. Decide which scope is right. Ask whether every tower provides its own (per tower) or the project provides one for everyone (project-wide).
  2. To list it project-wide when towers already have it: on the Per-tower amenities card, click the bin icon (Remove <amenity>) on the amenity in every tower box and confirm Remove ("It is removed from tower <name> only."). Then click Add amenity on the Project-wide amenities card and add it once.
  3. To list it per tower when it is project-wide: on the Project-wide amenities card, click the bin icon on the amenity and confirm Remove ("It is removed from the project."). Then click Add on each tower's box (or Add on a tower and pick the tower) and add it once per tower.
  4. If Add on a tower is greyed out and the card reads "No towers yet", add towers on the Structure tab first.

Editing a row and switching its Scope is refused by the same rule, so remove and re-add rather than trying to convert a row in place.

Related

  • AmenitiesScreen

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

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

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

  • List amenities, project-wide or per towerHow-to

    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.

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

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