The builder
Who sees an element
Showing an element to everyone, members, guests or one user group, only while a collection field is set, or only on some devices, and how that differs from page access and button actions.
Role Visibility rules
- Select the element, open Role Visibility in its General tab and press Configure Rules.
- Choose who can see this element, and press Save Rules.
| Rule | Who sees it |
|---|---|
| Everyone (Always Visible) | Every visitor. |
| Logged In Users Only | Signed-in members. |
| Logged Out Users Only | Signed-out visitors. |
| One audience only | Signed-in members in the chosen user group. Click a chosen audience again to clear it. |
| While a collection field is set | On a collection page or a card: only entries whose chosen field isn't empty, false or 0. |
In the app: Properties › General › Role Visibility
How it works
Hidden elements are removed on the server before the page is sent: they are not in the page's HTML at all, so nobody can reveal them with the browser's tools. In the builder every element shows, whatever its rule; check with Preview signed in and signed out on the live site.
Audiences are the website's user groups. Manage audiences in the picker opens the group editor. A user group that was deleted shows a warning: choose another or clear it.
Hiding on a device
Device visibility is in the Style tab instead: Visibility & classes › Desktop, Tablet, Mobile. It hides the element with CSS on that screen size, so it is still in the page. Use it for layout (a long menu on desktop, a short one on phones), not for anything private.
Visibility, access and actions compared
- Page access
- Who may open a whole page: others get the 401 or 403 screen. In Page Settings.
- Overlay access
- Who gets an overlay at all. In Edit Overlay.
- Element visibility
- Who sees one element on a page everyone may open. This page.
- Interaction modes
- One element, a different click for each kind of visitor: Button actions and interactions.
- Entry audiences
- Which entries of a collection a visitor sees: Collection entries.
In your own HTML
Inside a Rich Text / HTML element, any tag can carry visibility-rule="logged_in_only" (or logged_out_only, or user_specific with audience-key="the group's id") and is removed the same way for visitors it isn't for.
A price for members only
Worked example: Members see the price, guests see a reason to join
- Add a Price showing 49 and set its Role Visibility to Logged In Users Only.
- Beside it, add a Button Join to see prices with Logged Out Users Only and the action Navigate to Link › /register.
- Pro members get a third element, Your price: 39, with One audience only › Pro members.
Ideas to try
- A Featured badge on collection cards with While a collection field is set › featured.
- A Welcome back, {{userEmail}} line for members only at the top of the home page.
- A Verify your email banner for the Email not verified group, with a Request Email Verification button.