Authorizing your app on a per-screen basis improves security by ensuring that users access only the required screens. The visibility of screens can be adjusted based on the roles you create.
For example, you can make the Department page visible only to users with the Administrator role. A user in the staff role cannot view this page.
2.1. Role Based Authorization on Screens
When authorizing screens, you can use the Authorization field in the Properties panel. To make the screen visible only to a specific role, you can set the visibility of that screen by adding that role.
2.2. Authorization in Preview Mode
When you preview the application you developed, you must activate the All Roles Access Switch so that users can log in. Thus, users can view the authorized screens by entering their e-mail and password on the login screen of the application.
If you want the screens to appear without requiring login, simply enable the Anonymous Access Switch. In this case, users can view the screens without the need to log in.
Authorization for screens and elements increases the security and functionality of the application by ensuring that users only access the areas that are appropriate for their role. Creating roles correctly and defining appropriate access rights for each element or screen improves user experience and efficiency.
