Page Access Control

Overview

Bellini provides two layers of access control for pages: a public/private toggle that requires users to be logged in, and scope restrictions that limit access to users belonging to specific groups. Both settings appear in the Properties view when authentication is enabled on the application.

What You Will Learn

How to set a page as public (authentication is required by default when enabled on the app)
How to configure scope restrictions on a page
How Bellini enforces access when a user does not meet the requirements
How the navigation component responds to scope settings

When To Use This

Use this page when you need to restrict access to one or more pages in an authenticated Bellini application — either to logged-in users only, or to a specific subset of users based on their group membership.

Prerequisites

Authentication must be enabled on the application. When it is, the Authentication Required and Scopes properties appear automatically in the page's Properties view. See Page Configuration.

Public vs Private Pages

When authentication is enabled on an application, all new pages are private by default — users must be logged in to access them. You can override this on a per-page basis by toggling Authentication Required off to make a specific page publicly accessible without login.

Making a Page Public

Open the page in the Page Editor.
In the Elements Tree, click the top-level item named after your page.
In the Properties view, toggle Authentication Required off.

When Authentication Required is off, the page is accessible to anyone without login.

When Authentication Required is on (the default), users who are not logged in are redirected to the Lonti SSO login page. After a successful login, they are redirected back to the original page, including any query parameters that were present in the URL.

Page Scopes

Scopes allow you to restrict a private page to users who belong to specific groups. Each app user is assigned scopes in the Lonti Console user directory, corresponding to the groups they belong to. When scopes are configured on a page, the user must have all of the configured scopes to gain access.

Configuring Scopes on a Page

Open the page in the Page Editor.
In the Elements Tree, click the top-level item named after your page.
In the Properties view, locate the Scopes field.
Type a scope name and press Enter to add it as a chip. Repeat for each scope required.

The scope names must match the group names configured in the Lonti Console user directory for your organization.

Scope Enforcement

When a user accesses a scope-restricted page, Bellini checks whether their assigned scopes match all of the scopes configured on the page:

Match — the user accesses the page normally.
No match — Bellini displays an access denied page with a button to go back.

The built-in navigation component respects page scopes automatically. Pages that a user does not have the required scopes for are hidden from the navigation menu. This means scopes serve a dual purpose: enforcing access control and keeping the navigation clean for each user.

Helpful Resources

Page Configuration — Full reference for page properties including Authentication Required and Scopes
Page Routes — How query parameters are preserved across page navigation and post-login redirects
Lonti Console — Manage user groups and scope assignments
Community Q&A: Bellini Community
Have a question? Post or search it here.