Two settings you will rarely need day to day: Custom Class, a hook for designers, and Access Control, which shows a component only to visitors with certain roles.

Custom Class

Custom Class is the last field of the light-blue Config row. It is a plain text field that adds a CSS class name to the component’s outer wrapper on the page.

The Config row of an Accordion: Target Placement, Color Style, Component Width and an empty Custom Class text field, followed by the Open first item switch.
Custom Class is the last field of the Config row.
  • Leave it empty unless a designer or developer asks you to type something specific. On its own, a class name changes nothing; it only works when the site theme contains a matching style rule.
  • Type only what you were given, for example highlight-box or compact spaced. Class names contain letters, digits and hyphens; several names are separated by spaces.
  • Typical uses: a one-off spacing tweak, a special background pattern, hiding the component in print, or hooking a component for site analytics.
  • Do not use Custom Class to fix layout problems you can solve with Component Width, Columns or Container Settings.

Access Control

Access Control restricts who can see a component according to the visitor’s user role. It is a collapsed section of the component card, below the items.

Access Control is not enabled on every component or on every site. On the demo site it currently appears on the Image Gallery only; ask your administrator if you need it elsewhere.

The Access Control section expanded: a choice between Allow the selected below and Restrict the selected below, then role checkboxes for Anonymous user, Authenticated user, Content editor and Administrator, with the note that if no roles are selected access falls back to neutral.
The Access Control section on an Image Gallery.

How it works

  1. Choose the mode:
    • Allow the selected below — only visitors who have at least one of the ticked roles see the component.
    • Restrict the selected below — visitors who have any of the ticked roles do not see the component; everyone else does.
  2. Tick one or more roles. The roles are combined with OR: having any one of them is enough.
  3. If you tick no role, the setting is neutral and the component is visible to everyone, whatever the mode.

The check applies to viewing only. Editing permissions are unchanged, and users who hold the site-wide permission to bypass this kind of restriction (typically administrators) still see the component.

Examples

GoalModeRoles ticked
Members-only download linksAllow the selected belowAuthenticated user (plus any member roles)
A “Log in to see more” teaser shown only to visitors who are not logged inAllow the selected belowAnonymous user
Hide a draft component from the public while editors review itAllow the selected belowContent editor, Administrator
Hide an internal notice from anonymous visitorsRestrict the selected belowAnonymous user

Tips

  • Access Control hides the component entirely, including its section title. If you want a visible placeholder, add a second component with the opposite rule (for example an anonymous-only “Log in to see this content” text).
  • Remember that Published (see Section Title and Intro Text) is the simpler tool when you just want to hide a component from everyone.
  • When checking the result, log out or use a private browser window: as an editor or administrator you will usually see everything.