"No access" or "You do not have permission": your role lacks a permission
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.
Messages this explains
- “No access”
- “You do not have permission to view <screen>. Ask your administrator.”
- “You do not have permission to do that.”
- “Missing permission: <MODULE>:read”
- “You do not have permission to view any settings section. Ask your administrator.”
- “Needs the Lookups permission.”
- “Needs the Structure permission.”
- “Picking a tower needs the Structure permission.”
- “Needs the Projects permission.”
- “Needs the Companies permission to pick or create one.”
- “Needs the Companies permission to pick or create one; leave for an administrator.”
- “Needs the Users permission to pick an owner.”
- “Listing users needs the Users permission; ask an administrator to assign this opportunity.”
- “Picking a project needs the Projects permission.”
- “Picking a unit needs the Structure permission. Ask someone with it to price this opportunity.”
- “Pricing plans and live pricing need the Pricing permission; only hand-added charges are possible.”
- “Picking parking needs the Parking permission.”
- “Choosing a contact type needs the Lookups permission.”
- “Choosing a company type needs the Lookups permission.”
- “Choosing a parking type needs the Lookups permission.”
- “Choosing an activity type needs the Lookups permission.”
- “Listing amenities needs the Lookups permission.”
- “Searching <kind> needs read access to that module.”
- “Needs the Bank Accounts permission.”
- “Picking the company needs the Companies read permission.”
- “Choosing a set of books needs the Books read permission. Ask your administrator.”
- “Linking a society needs the Projects update permission.”
- “Changing the person's name or phone needs the Contacts update permission.”
- “Adding lines needs read access to Charge Components and Bookings (payment cadences). Existing lines are shown; new ones cannot be picked.”
- “Adding lines needs read access to Charge Components. Existing lines are shown; new ones cannot be picked.”
- “Adding lines needs read access to Bookings (payment cadences). Existing lines are shown; new ones cannot be picked.”
- “Allotting units needs the Structure permission.”
- “Benefit plans need the Pricing permission”
- “Adding charges needs the Charge Components permission; existing lines can still be edited.”
- “Linking groups to stages needs the Construction Stages permission.”
- “The payment schedule preview needs the Bookings permission.”
- “A construction-linked preview needs the Construction Stages permission.”
- “Milestone-linked rows need the Milestones permission to list the project's milestones.”
- “Creating the ledgers needs permission to edit projects”
- “Editing opening balances needs the Chart of Accounts update permission.”
- “Appropriating needs permission to update demands”
- “Posting a revenue run needs REVENUE:approve”
- “Only a user allowed to approve revenue (REVENUE:approve) can change the policy.”
- “A Finance Lead (PAYMENTS:approve) approves the run before the bank file is exported.”
- “Searching companies needs the Companies permission; the booking's partner is used.”
- “Tower names need the Structure permission; rows are still listed.”
- “Needs access to <MODULES>”
- “You can view the structure but not add towers or units. Continue, or ask someone with the Structure permission.”
- “Without the Projects permission every project of the company is mirrored.”
- “You can see this workflow but lack the permission to start it (WORKFLOW_RUNS:create).”
- “Nothing to choose from.”
"No access" or "You do not have permission": your role lacks a permission
A page shows a No access card, an action was refused, a button is greyed out, or a dropdown is disabled with a note naming a permission. In every case your role does not hold the permission the screen, action or picker needs.
What you see
A whole screen. A card headed "No access" with "You do not have permission to view <screen>. Ask your administrator." (the screen named in the app's own words: "projects", "bookings", "payments", "charge components", "booking creation", "opportunities and estimates (needed to book)"). The Settings hub shows "You do not have permission to view any settings section. Ask your administrator." when none of its sections is open to you. The sidebar only lists the groups and entries you can view, so a screen you cannot reach is usually missing from it rather than blocked (see Sidebar, top bar and notifications bell).
An action. The red banner or toast "You do not have permission to do that." when the server refuses a save, delete or transition. Through the AI connector the reply starts "Missing permission:" and names the permission needed (or "one of" several when any of them would do).
A greyed-out button with the reason on hover (see Greyed-out buttons), for example "Creating the ledgers needs permission to edit projects" on Sync bank ledgers, "Appropriating needs permission to update demands" on a demand's lines, a reason naming the approve permission on revenue on a revenue run's Post run, "Benefit plans need the Pricing permission" on an offer. Some pages explain in a note instead: "Editing opening balances needs the Chart of Accounts update permission.", "Linking a society needs the Projects update permission.", "Changing the person's name or phone needs the Contacts update permission.", "Without the Projects permission every project of the company is mirrored." Three notes name the permission in its short technical form: on the revenue policy (only a user allowed to approve revenue can change it), on a Draft payout run (a Finance Lead approves the run before the bank file is exported) and on a workflow you can see but not start.
A disabled picker. A dropdown or search that lists records from another module is disabled, with the reason as its placeholder, hint or an amber note: "Needs the Lookups permission." (amenities, lead sources, bank account purposes), "Needs the Structure permission." (preferred tower) and "Picking a tower needs the Structure permission." (a per-tower amenity), "Needs the Projects permission." (a cost centre's project), "Needs the Companies permission to pick or create one." (channel partner; on a project's promoter "…; leave for an administrator."), "Needs the Users permission to pick an owner." and "Listing users needs the Users permission; ask an administrator to assign this opportunity.", "Picking a project needs the Projects permission.", "Picking a unit needs the Structure permission. Ask someone with it to price this opportunity.", "Pricing plans and live pricing need the Pricing permission; only hand-added charges are possible.", "Picking parking needs the Parking permission.", "Choosing a contact type / company type / parking type / an activity type needs the Lookups permission.", "Listing amenities needs the Lookups permission.", "Searching <kind> needs read access to that module." (the party or owner picker on ledgers and bank accounts), "Needs the Bank Accounts permission." (a bank ledger's account), "Picking the company needs the Companies read permission." (new books), "Choosing a set of books needs the Books read permission. Ask your administrator." (every accounting screen), "Adding lines needs read access to Charge Components and Bookings (payment cadences). Existing lines are shown; new ones cannot be picked." (or only one of the two modules) and "Allotting units needs the Structure permission." (an offer), "Adding charges needs the Charge Components permission; existing lines can still be edited." and "Linking groups to stages needs the Construction Stages permission." (a pricing plan), "The payment schedule preview needs the Bookings permission." and "A construction-linked preview needs the Construction Stages permission." (the plan preview), "Milestone-linked rows need the Milestones permission to list the project's milestones." (a payment plan), "Searching companies needs the Companies permission; the booking's partner is used." (a commission), "Tower names need the Structure permission; rows are still listed." (amenities). A picker that has nothing to offer at all reads "Nothing to choose from." (a campaign audience or a rule's picker), which is an empty list rather than a permission problem.
The project setup wizard. A step you cannot open is marked No access with the tooltip "Needs access to <MODULES>", and the structure step warns "You can view the structure but not add towers or units. Continue, or ask someone with the Structure permission." (see Project setup wizard).
Why it happens
Every permission is a module and an action. The role editor lists the modules by group (Organization, Projects, CRM, Masters, Accounting, Documents, Workflows) and the actions View, Create, Edit and Delete, plus the special actions some modules have: Approve on Estimates, Payments and Revenue Recognition, Issue on Demands, Post on Vouchers, send on Campaigns and publish on Document Templates (these two columns are headed in lower case). A screen opens with View on its module; each button needs the action it performs; and a picker that lists records from another module needs View on that module, because listing them is itself a read of that module. That is why an opportunity form can be open to you while its Assigned to list stays disabled, or an offer can be edited while new lines cannot be picked.
Each user holds exactly one role, and the role is what grants permissions, so a permission arrives by changing the role or by moving the user to another role. The Administrator role always holds every permission. The other seeded roles are starting points (Finance Lead, Accountant, Sales Manager, Sales Executive, Project Manager, Site Engineer, Rehab Officer, Compliance Officer, Auditor, Front Desk, Legal & Documentation), and an organization can edit them or add its own. The approve rights are deliberately separate from Edit, so that the person who records money or prepares a run is not the one who signs it off.
Names in the messages are the module names as the role editor shows them, with two older spellings: "the Structure permission" means Towers, Floors & Units, and "the Milestones permission" means Construction Stages. The few messages that quote a permission in its short technical form (posting a revenue run, changing the revenue policy, approving a payout run, starting a workflow) mean Approve on Revenue Recognition, Approve on Payments and Create on Workflow Runs.
How to fix it
- Work out which permission is missing. The message names it: the module ("Lookups", "Companies", "Books") and the action ("read" or "view", "update" or "edit", "create", "approve"). A No access card on a screen means View on the screen's module.
- Ask an administrator (anyone with the Edit permission on Roles & Permissions; in the default roles the Administrator) to grant it. On Roles & Permissions they open your role with Edit role, tick the action on the module, and save. The change applies to everyone who holds that role. If that is too broad, they can create a role for your job with New role and move you to it on Users (the Edit permission on Users); a user has one role, so the new role must carry everything you need.
- Or hand the step to someone who has the permission. The messages often say so: "Ask someone with it to price this opportunity", "ask an administrator to assign this opportunity", "leave for an administrator". Approvals in particular are meant to be done by a different person: a Finance Lead approves a payout run and posts a revenue run, a Sales Manager approves an estimate.
- Reload the page after the role changes so the screen picks up the new permissions; the sidebar, buttons and pickers follow what your role holds.
- "Nothing to choose from." is not a permission problem: the list is empty. Add the values (a campaign audience, a lookup, a project) and reopen the picker.
Related
Related
- Greyed-out buttonsScreen
Why a button is grey and can't be clicked, where to read the reason, and why some buttons are missing altogether.
- Roles & PermissionsScreen
The list of your organization's roles: open one, create or clone a role, deactivate or reactivate it, and delete custom roles nobody holds.
- Edit roleScreen
Change a role's name, description, active flag and permissions, see who holds it, and open its History.
- New roleScreen
Name a new role, describe it and tick what it may do in each module, then create it so it can be given to users.
- 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.
- SettingsScreen
The Settings area of the app: a row of tabs for your organization's profile and policies, products, users, roles, lookups, workflows, documents, AI connectors and the audit log.
- Sidebar, top bar and notifications bellScreen
The frame around every page once you are signed in: the sidebar with its groups, the top bar with the notifications bell, the light and dark switch and your account menu, and the banners that ask you to act.
- 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.
- 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.