The visibility tab provides a powerful tool to control access to information and functionalities within your application.
This article explains how to control who sees specific elements within your application using the visibility tab in the Application Builder.
Learn more about page visibility to control which user groups can see specific pages in your application.
The visibility tab allows you to define which user groups can view specific elements in your application according to a user’s authentication status. This is helpful for situations where you want to:
You can set a different visibility level for each element in your application. This allows you to create a customized user experience based on login status.
Visibility roles provide a granular level of control over user access. By defining roles within your application and assigning them to users, you can determine which elements each user can see.
Before using visibility roles, you’ll need to establish the different user roles within your application.
Create a field in the table to store the assigned role for each user based on their permissions.
In the Application Builder, navigate to your User Source settings. There, you’ll define a role field. This field will be used to map user data in your User Source to the roles you established. or use the default role to assign appropriate roles to each user.
Navigate to the element’s Visibility tab within the editor. This allows you to define visibility based on user roles:
This empowers you to create custom user experiences tailored to different user types.
We’re constantly enhancing the security features of the Application Builder.
While you can hide elements within your application to control what users see in the user interface (UI), the underlying data might still be technically accessible through the API.
This means that even if an element is hidden, restricted users might still be able to access the data it represents using the API. When retrieving data through the API, all fields for all rows are returned by default, regardless of what’s visible in the UI. This applies to all fields in the application, not just those displayed on the page.
This is a temporary limitation, and we’re actively working on implementing robust security measures. In the meantime, please be cautious about storing sensitive data within your applications until these security improvements are in place.
Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions—we’re ready to assist you.