NirmaanOne Help
TroubleshootingReviewed 2026-09-29

Cancel booking fails on the last step: it needs Edit on Demands and Create on Payments

Opening the cancel wizard needs only the Edit permission on Bookings, but posting the cancellation also writes credit notes and a refund payout, so it needs the Edit permission on Demands and the Create permission on Payments as well. With the default roles only the Administrator holds all three.

Messages this explains

  • “You do not have permission to do that.”

Cancel booking fails on the last step: it needs Edit on Demands and Create on Payments

You worked through the Cancel booking wizard, entered a reason on the Confirm step and clicked Cancel booking, and the page answered with a permission error. Nothing was cancelled.

What you see

After you click Cancel booking on the Confirm step, a red alert under the step bar reads "You do not have permission to do that." The booking stays Active and nothing is posted.

Why it happens

The wizard does two kinds of work, and they are checked separately:

  • Opening the wizard and seeing its figures needs only the Edit permission on Bookings, the same permission as the Cancel booking button on the booking.
  • Posting the cancellation changes the accounts as well as the booking: it reverses the demands with credit notes and creates the refund as a pending payout. So it also needs the Edit permission on Demands and the Create permission on Payments. This applies to every cancellation from the wizard, even one with no demands or money.

This keeps the money side of a cancellation with the people allowed to raise demands and record payments. With the default roles, only the Administrator holds all three permissions. A Sales Manager or Legal & Documentation user can open the wizard and reach the last step but can't post it; the Finance Lead and Accountant can't open the wizard at all, because they can only view bookings.

How to fix it

  1. Hand the cancellation to someone who holds all three permissions: the Edit permission on Bookings, the Edit permission on Demands and the Create permission on Payments. With the default roles, that is an Administrator. The figures you entered are not saved, so they re-enter the forfeiture, charges, refund and reason.
  2. Or give a role all three. Someone with the Edit permission on Roles & Permissions opens the role on Edit role (from Roles & Permissions) and ticks the missing permissions, for example Edit on Demands and Create on Payments for the Sales Manager, or Edit on Bookings for the Finance Lead, then clicks Save role. The Administrator role can't be edited; it already holds everything.
  3. Or move the user to a role that has them, with Edit role & access on Users (the Edit permission on Users).
  4. The new permissions reach the user when their session is next renewed (within about 15 minutes), or at once if they sign out and in again. Then open Cancel booking again from the Booking overview and confirm.

Related

  • Cancel bookingScreen

    The four-step wizard that cancels a booking: it shows the demands and receipts that will be reversed, suggests the forfeiture and charges from the rule in force, sets the refund and posts everything in one go, releasing the unit and parking and marking the opportunity lost.

  • Booking overviewScreen

    A booking's home page: the applicant and unit, parking, dates, money summary, termsheet status and possession, with the buttons to edit the booking, see its history, jump to the opportunity or cancel it.

  • Edit roleScreen

    Change a role's name, description, active flag and permissions, see who holds it, and open its History.

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

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

  • Roles and permissionsConcept

    What a permission is (a module plus an action), how roles bundle permissions, the twelve default roles and what each is meant for, the one-role-per-user rule, and when a change reaches a signed-in user.

  • Booking cancellation, forfeiture and refundConcept

    Cancelling a booking reverses its demands with credit notes, posts the forfeiture and any charges against the buyer's ledger by the rule in force, creates the refund as a pending payout for the credit that is left, and frees the unit and parking; with nothing billed or received it only frees them.

  • Booking cannot be cancelled yet: pending payments, or revenue already recognisedTroubleshooting

    The cancel wizard stops on its first step while a receipt or payout on the booking is still Pending, while revenue on the booking is recognised under a policy that does not allow cancelling, or when the booking is already cancelled.

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