Skip to content
Tutorials Center
My learning

Topics

Lesson 24 of 37 ยท Users and Access

Permissions and Inheritance

Master the Joomla permission system: actions, Allowed, Denied and Inherited states, the asset hierarchy from global configuration to a single article, and why Deny always wins.

Viewing levels decide what a visitor can see. Permissions decide what a logged-in person can do: log in to the back end, create an article, edit someone else's article, publish, delete, change a component's options. Joomla's permission system is an access control list (ACL) that is both flexible and precise, and it is the reason Joomla is popular for sites with editorial teams.

Joomla cannot run on this site, so this lesson explains the rules in words and then implements them in a short JavaScript stand-in that you can run and modify. The rules are the real ones: once you understand them, the permission screens stop being mysterious.

Actions

A permission is an answer to the question: may this group perform this action here? The common actions are:

Action Meaning
Site Login / Administrator Login May log in at the front or the back end
Offline Access May log in while the site is offline
Super User Everything, everywhere
Access Administration Interface May open a component in the back end
Create May add new items
Delete May delete items
Edit May edit any item
Edit State May publish, unpublish, trash
Edit Own May edit items they created

Some components add actions of their own (for example, Banners or Menus). The names inside the database look like core.create, core.edit.own, core.edit.state.

Three states

On every permissions screen each group has one of three settings per action:

  • Inherited: take the value from the level above (the default).
  • Allowed: this group may do it here.
  • Denied: this group may not, and nobody can allow it further down.

Next to it a Calculated Setting column shows the result after all rules are applied: Allowed, Not Allowed, or Not Allowed (Locked). "Locked" appears when a Deny above makes the choice impossible to change.

The hierarchy of assets

Every object that can carry permissions is an asset with a place in a tree:

flowchart TD
    G["Global Configuration"] --> C["Component options (Articles)"]
    C --> K["Category (News)"]
    K --> S["Subcategory (Press)"]
    S --> A["Article (single item)"]

Permissions flow downward through this chain.

You can set permissions at the Global Configuration (Permissions tab), in a component's Options, in a category, and in a single article. The default value at the top for ordinary actions is Not Allowed (Inherited), and the default install allows, for instance, Author to create articles through settings on the Articles component level, Editor to edit and Publisher to change state.

Inheritance works along two lines at once:

  1. Down the asset chain: a category inherits from its component, an article from its category.
  2. Up the group tree: a group inherits from its parent group (Publisher from Editor, Editor from Author, and so on).

The rules, step by step

  1. An explicit Allowed at some level gives the group the right at that level and below, unless a Deny exists.
  2. An explicit Denied at any level and for any group in the user's ancestry beats everything. It is inherited by child groups and child assets and cannot be overridden lower down.
  3. Inherited means "no opinion here"; if no level gives an opinion the answer is Not Allowed.
  4. If a user is in several groups, a Deny from any of them wins over the Allows of the others.
  5. Super User (the Super User action granted at the global level) short-circuits everything.

Consequences you can use:

  • To give one group more rights in one category, set Allowed for it in that category. You do not touch the rest of the site.
  • To remove a right that a parent group has, Deny is blunt: it also affects all child groups. Often it is better to stop inheriting by moving the group in the tree.
  • Never Deny a right to Public or to Registered unless you mean it for everyone: all other groups inherit from them.
JS A tiny permission resolver

Press Run (or Ctrl + Enter) to see the console output here.

No output.

In the demo, Editors may edit article 7 (the global Allow), but article 42 sits in the legal category where Registered is denied: Editors, Authors and Publishers all inherit that group Deny, and the Allow set directly on the article for Authors is ignored.

Edit own and workflow

Authors normally cannot edit other people's articles but can edit their own, thanks to Edit Own. This right needs the item's created_by to match the user. Joomla 4 and later also have optional Workflows, where publishing happens through stages and transitions that have their own permission settings; without workflows enabled, the classic Edit State action is used.

Admin interface rights

Being able to log in to the back end is not enough. A group also needs Access Administration Interface on every component it should open. A typical pattern for editors: Administrator Login allowed, Access Administration Interface allowed only for Articles, and nothing for Users, Extensions or Global Configuration. That keeps front-end editors from changing the system.

A permissions checklist

When something "does not work", walk this list:

  1. Is the user in the group you think? (Check Users > Manage, and the user must log in again after a change.)
  2. Is there a Denied anywhere along the chain, for any of their groups? The calculated column says "Locked" when so.
  3. Is the right set at the right level (global versus component versus category)?
  4. For editing own items: is the user the author of the article?
  5. For viewing: is the viewing access level right too? A permission does not make hidden content visible.
JS Explain a denied action

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. A group has Denied for Edit in a category and Allowed for Edit on one article in it. Can they edit the article?

    Deny wins at any level; a lower-level Allow cannot undo it.
  2. 2. What does Inherited mean on a permission setting?

    Inherited means no opinion here, so the value flows from the parent asset (and parent group).
  3. 3. Which permission lets an author change only their own articles?

    Edit Own applies to items the user created.
  4. 4. Why is it risky to Deny something to the Registered group?

    Child groups inherit from Registered, so the Deny propagates and cannot be overridden by them.
  5. 5. A user can edit an article but cannot see it on the front end. What else should you check?

    Permissions and viewing levels are separate; check Access on the item.

Summary

  • Permissions are per action (create, edit, edit own, edit state, delete, admin access) and per group.
  • Each setting is Inherited, Allowed or Denied; Calculated Setting shows the result.
  • Permissions flow down the asset chain (global, component, category, article) and up the group tree.
  • Deny always wins and cannot be overridden lower down; Super User bypasses everything.
  • Set rights as high as makes sense and exceptions as low as possible.

Next: Registration, Login and Privacy