Why a Permission Won't Turn On or Off

3 min read

Published August 28, 2026

Updated August 29, 2026

The five reasons a change is refused

Every refusal names the other permission involved, so you always know what to change next.

  • Needs another permission: the action cannot work without it. Offered as 'Turn on all'.
  • Something depends on this: switching it off would strand another permission. Switch those off first.
  • Data scope too narrow: a report or export would show more than the person can see.
  • Not in your plan: the feature belongs to a paid plan.
  • Owner only: permanently locked, for the two permissions that could bypass everything else.

The 'Turn on all' button

When a permission needs others, Fixmo works out the full chain, including prerequisites of prerequisites, and offers to switch them all on together. It never does this silently, and it never includes a locked permission, so the button cannot be used to grant something that is meant to stay with the owner.

Frequently asked questions

Some actions cannot work on their own. 'Add parts to a repair' needs 'View repairs' and 'View inventory', because you cannot put a part on a job you cannot open, taken from a catalogue you cannot see. When you switch on something with missing prerequisites, Fixmo offers a 'Turn on all' button that switches on everything it needs in one go.

Because something else that is still on depends on it. Switching off 'View invoices' while 'Create invoice' is on would leave a permission that can never be used. Fixmo names the permissions that depend on it so you can switch those off first. It does not switch them off for you, because removing access you did not ask to remove would be worse than the error.

You are switching on a report or an export that totals more records than that person's data scope allows them to see. For example, giving someone the Repairs report while their Repairs scope is Own. Widen the scope to Branch or All first, or leave the report off.

Two permissions can never be granted to anyone: changing a person's role, and erasing shop data. Either one could be used to step around every other permission on the page, so they stay with the shop owner permanently. They are shown rather than hidden so the reasoning is visible.

Some features belong to paid plans, such as WhatsApp messaging, Website Sync, bulk invoicing and estimate versioning. The permission cannot be switched on for a plan that does not include the feature. If you upgrade, the permission becomes available. If you downgrade, permissions you already set are kept but the feature itself still refuses, so nothing silently changes.

That is a segregation of duties warning, not a block. It appears when one person would be able to do both halves of a money control, such as raising a refund and approving it. In a small shop that is often unavoidable, so Fixmo lets you proceed, and records in the change log that the risk was accepted.