How Joomla Permission Inheritance Works

Joomla permissions are evaluated through two related hierarchies: the user-group hierarchy and the asset hierarchy for the item being accessed. Understanding both explains why a permission that looks Allowed on one screen may still calculate as Denied for a particular user.

Joomla permission inheritance is calculated through both the user-group hierarchy and the asset hierarchy. A permission shown as Allowed on one screen can still be effectively Denied when another applicable rule blocks it, so always evaluate the calculated result for the actual user and action.

Understand the two inheritance paths

User groups can inherit from parent groups, while Joomla assets can inherit rules from higher levels such as Global Configuration, a component, a category, and an individual item. Both paths can affect the final authorization decision.

Follow user-group inheritance

A user may belong to several groups, and child groups participate in permissions inherited from their parent chain. Choosing a parent for a custom group is therefore a security decision. Before assigning users, inspect what the parent already grants or denies.

Follow the asset hierarchy

For supported actions, Joomla can evaluate permissions from higher assets down to the target. For article editing, for example, relevant rules may exist globally, in the Articles component, in a category, and at the article level. A lower setting must be understood in the context of the rules above it.

Know what Inherited means

Inherited does not mean Allowed. It means the current level does not add an explicit Allowed or Denied rule for that group and action. Joomla continues evaluating applicable inherited rules. Save the permission screen and inspect the Calculated Setting to see the effective result.

Remember that Denied has priority

An explicit Denied in an applicable path cannot simply be overridden by setting Allowed lower in the hierarchy. If a permission unexpectedly remains Denied, search parent groups, other groups assigned to the user, and higher assets for an explicit denial before adding more Allowed rules.

Troubleshoot inheritance step by step

  1. Identify the exact user and every group that applies.
  2. Identify the exact action, such as Create, Edit, Delete, or Edit State.
  3. Check the group hierarchy, including parent groups.
  4. Inspect permissions from Global Configuration through the relevant component, category, and item.
  5. Look specifically for an explicit Denied rule.
  6. Save changes and review the Calculated Setting.
  7. Retest with the affected non-Super-User account.

Keep visibility separate from action permissions

Viewing access levels determine what a user may see. ACL action permissions determine what a user may do. A user can be allowed to view an article while still being unable to edit it, so troubleshoot those layers separately.


Need More Help with Joomla?

Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.

Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.

QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.

Open a Support Ticket