Allowed vs Denied vs Inherited Permissions in Joomla
Joomla permission screens commonly present Allowed, Denied, and Inherited. These values are not three equal states. They participate in Joomla's ACL hierarchy, and the effective result depends on the user's applicable groups and the permission rules above the current asset.
Joomla permission screens use Allowed, Denied, and Inherited, but the effective permission depends on the full ACL hierarchy. Read the selected value together with Joomla's calculated setting rather than treating one dropdown as the final answer.
Allowed explicitly grants an action
Allowed grants the selected action to the group at that level when no applicable Denied rule blocks it. Use it when the role genuinely needs the capability and the surrounding inheritance model supports that grant.
Denied explicitly blocks an action
Denied is restrictive and has priority in the applicable permission path. A lower Allowed rule does not cancel an explicit Denied above it. Use Denied carefully because it can affect child groups and lower assets in ways that are easy to overlook.
Inherited defers to other applicable rules
Inherited means the current level does not explicitly grant or deny the action for that group. Joomla evaluates relevant parent-group and higher-asset rules to determine the effective result. Inherited can therefore calculate to either Allowed or Denied.
Use Calculated Setting after saving
- Change the permission only at the level you intend to configure.
- Select Save.
- Review the Calculated Setting for the group and action.
- If the result is unexpected, inspect inherited rules before making another change.
When Allowed still calculates as Denied
Check the selected group's parents, higher levels in the asset hierarchy, and every other group assigned to the user. An explicit Denied in any applicable path can explain why a local Allowed selection does not become the effective permission.
Choose the least complicated rule
- Use Allowed when the role requires the action.
- Leave Inherited when the higher-level policy already produces the correct result.
- Use Denied only when the action must be blocked and you understand the inherited effect.
A simpler hierarchy is easier to audit and troubleshoot than layers of conflicting grants and denials.
Do not confuse ACL actions with viewing access
These permission states govern actions. An item's Access field and its viewing access level govern visibility. If the complaint is that a user cannot see an item, inspect viewing access 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.