Skip to content
Tutorials Center
My learning

Topics

Lesson 23 of 37 ยท Users and Access

Users, Groups and Viewing Levels

Learn how Joomla organizes people: users, the default group tree, viewing access levels, and how the Access field decides who sees an article or module.

A website with only anonymous visitors needs no accounts. The moment you want editors who write articles, members who see private pages or customers who log in, you need a model that says who may do what and who may see what. Joomla's model is one of its strongest features, but it surprises people because it has two separate dimensions: what a person can see, and what a person can do. This lesson covers the first and the building blocks of both; the next lesson covers the second.

Joomla cannot run on this site, so we describe the screens by menu path and use JavaScript stand-ins to make the logic tangible.

Users

Every account lives in Users > Manage. A user has a name, a username, an email address, a password (stored only as a hash), a status (enabled or blocked), an activation state and, most importantly, membership in one or more groups. Further tabs hold the user's language, editor and time zone preferences, and custom field values if you defined user fields.

A person who is not logged in is a guest; Joomla still evaluates what a guest may see, using the built-in groups Public and Guest. Blocking a user keeps the account and its authored content but stops logins, which is safer than deleting.

The group tree

Users > Groups shows a tree. Each group has a parent, and the key rule is: a group inherits from its ancestors. A fresh Joomla installation contains these groups:

flowchart TD
    Public["Public"] --> Guest["Guest"]
    Public --> Manager["Manager"]
    Manager --> Administrator["Administrator"]
    Public --> Registered["Registered"]
    Registered --> Author["Author"]
    Author --> Editor["Editor"]
    Editor --> Publisher["Publisher"]
    Public --> Super["Super Users"]

The default group tree. Publisher inherits from Editor, Author, Registered and Public.

The front-end team is Registered, Author, Editor, Publisher: they differ in what they may do with articles (the next lesson). Manager and Administrator are back-end roles. Super Users have all rights everywhere and cannot be limited by permissions, so create very few of them.

You can add your own groups: for example Members under Registered, or Shop Staff under Manager. Put a new group under the lowest existing group that already has the rights it needs, because it will inherit them.

Viewing access levels

Groups answer "who are you?". Viewing access levels answer "who may see this?". A level is simply a named list of groups. Under Users > Access Levels you will find the defaults:

Level Meant for
Public Everyone, including guests
Guest Only visitors who are not logged in (for example a login prompt)
Registered Logged-in members
Special Back-office and editorial staff
Super Users Only super users

Almost every item in Joomla has an Access field: articles, categories, menu items, modules, banners, contacts and so on. The item is shown to a visitor only if the visitor belongs to at least one group that is part of that level. Because groups inherit, a Publisher also holds the rights of the Registered group below it in the tree, so a Publisher can see items set to Registered even though "Publisher" is not named in the level. Conversely, a level that lists Editor is visible to Publishers (child of Editor) but not to Authors.

There are three consequences worth remembering:

  1. A menu item with level Registered is hidden from guests. The link vanishes from the menu, and typing the URL gives a login prompt or a 403 depending on the settings.
  2. An article may be hidden while its menu item is visible, or the reverse. Joomla checks each object's own level, and the article inside a category blog is also filtered by category access.
  3. Modules obey it too. A "My account" module with level Registered is invisible to guests, which is how you build different sidebars for different audiences.
JS Which levels can a user see?

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

No output.

Run it and notice how the Publisher sees Registered and Special without being named: the walk up the tree is the inheritance. The level table here is invented for the demo; open your own Access Levels screen to see which groups yours contain.

Using levels in practice

Members-only section. Create a category "Members" with Access = Registered, publish articles in it and create a menu item of the Category Blog type with the same level. Guests see neither the menu entry nor the articles. Pair it with the registration and login flow.

Teaser for guests. Show a login module (Access = Guest) on a members-only landing page: visitors see the form, logged-in members do not.

Editorial-only notes. A module with level Special or a custom level like "Staff" carries internal notes visible only in the front end to staff.

Creating a custom level

  1. Go to Users > Access Levels > New.
  2. Name it, for example Members.
  3. Tick the groups that belong (the Members group, and any staff groups that should also see it).
  4. Save, then pick it in the Access dropdown of articles, modules or menu items.

Remember that adding a user to a group changes their access at next login. A user who is already logged in keeps the groups loaded in the session until it ends.

A tiny page-visibility simulator

JS Filter a page by access level

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

No output.

This stand-in already includes the groups inherited by each user (we listed them), so it shows only the filtering step Joomla performs on every query: the database query for articles contains access IN (levels of this user).

Common mistakes

  • Giving everybody the Super Users group "to make it work". Fix the real permission instead.
  • Hiding a page by setting only the menu item to Registered while the article's own level is Public: the article is still reachable through another link or the search.
  • Creating a level but forgetting to add the groups, so nobody sees the item, including you.
  • Editing the default groups' parents. Create new groups instead.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a viewing access level contain?

    A level is a named list of groups; an item with that level is visible to members of any of them.
  2. 2. A Publisher can see an item set to the Registered level. Why?

    Publisher sits below Editor, Author and Registered in the tree, so it also counts as a Registered member.
  3. 3. Which default level is meant for visitors who are not logged in?

    The Guest level is for visitors who are not logged in, such as a login form shown only to them.
  4. 4. When does a changed group membership apply to a logged-in user?

    Groups are loaded into the session at login, so the user must log in again.

Summary

  • Users belong to groups; groups form a tree and inherit from parents.
  • Viewing access levels are named lists of groups controlling who sees an item.
  • Articles, categories, menu items and modules each have their own Access field.
  • Build members-only areas with a restricted category, menu item and module.
  • Avoid overusing Super Users; create custom groups and levels instead.

Next: Permissions and Inheritance