When you create a portal in Formaloo, you can control who can view each page based on their login status or assigned user role—like Teacher, Student, or Admin.
This is ideal for managing internal systems such as student portals, HR systems, or support ticket platforms.
You should convert your app to a portal to manage access to different pages and data on your app.
📝 Additional insights:
Want to know how to turn your app into a portal?
Follow this step-by-step tutorial to learn how to enable portal mode, add login/signup functionality, and start managing users within your app:
👉 Step-by-step guide: How to create a portal
Step 1: Turn your app into a portal
Before you can restrict access or assign roles, your app needs to be in Portal mode.
Go to your app.
Click the ⚙️ Settings icon on the top-right.
Enable Portal mode.
💡 Enabling portal mode adds login and signup functionality, so users will need to log in to access your portal content.
Step 2: Create user roles
To control what different users can access, you need to define user roles.
In the app editor, go to the User Portal page.
Click on Edit base of the user form.
Add new roles like Student, Teacher, or Admin based on your needs.
📝 Roles determine what each user type can access or manage in the portal. For example, Teachers may be able to edit grades, while Students can only view their own data.
📝 Additional insights:
Want a detailed walkthrough?
👉 Check out this step-by-step guide: How to add user roles on your portal
Step 3: Assign roles to your users
Go to the Users Table inside the user portal page.
Find the user you want to edit.
Assign the appropriate role (e.g., Teacher or Student).
This role will be used to control access to specific pages later.
Step 4: Set page-level access permissions
In the app’s left-hand menu, click the three dots (
⋮) next to the page you want to restrict.Click Access.
Choose a Visibility Option:
Public – Everyone can view.
Non Logged-in Users – Only available before login.
Logged-in Users – Available to all users who log in.
Specific user access levels – Limit access based on user roles (e.g., only Teachers).
All team members – Only workspace team members can see this page.
Specific team access levels – Limit to team members with a specific workspace role.
💡 Pro Tip
For public pages like the Welcome page, the access is set to Public by default, meaning everyone can view it without logging in.
Visibility options and access levels
Here is a list of all visibility options and what they mean:
Public: By default, all pages are visible to the public.
Non Logged in users: Only users who aren’t logged in will see the page. It’s especially useful when you want to include some helpful guides and pages for non-users that aren’t relevant to the logged-in users.
Logged-in users: Only users who are logged in can view the page with this visibility config.
Specific user access levels: Make the page only available for specific user roles. When you choose this option, another option will show up so you can choose the roles that can access the page.
All team members: Only your workspace team members can access the app.
Specific team access levels: Only workspace team members with specific roles can access the page. When you choose this option, another option will show up so you can choose the roles.
✅ Example use case: Student management system
Students can only access their own data and grades.
Teachers can update attendance and input grades.
Admins can oversee and manage everything.
This setup allows you to maintain clear boundaries between what different users can see or do within the same portal.
📝 Manage everything in one portal or separate admin panels
You can manage all user roles and access controls in one centralized portal. But if you prefer to keep administrative tasks separate, you can also build a dedicated admin portal to manage your main portal more efficiently.
✅ Learn how to create and connect a separate admin portal:
👉 How to create an admin portal for ticket management