Page visibility rules
Set visibility rules to only show sidebar pages to certain app users.
Often it's important to set visibility rules for when certain pages or folders should be visible to which teammates in your Noloco app.
In this video, you'll learn how to:
Set visibility rules by user role
Preview as other app users to make sure your rules are applied
Create custom visibility rules
Learn more about Visibility Rules across Noloco 👇
Visibility SettingsField visibility conditionsTroubleshooting Page Visibility Issues
Pages Invisible Despite Correct Rules
If your pages aren't showing up in Live mode even though visibility rules look correct:
Publishing Required: Page visibility changes require republishing your app
Go to Settings > Publishing > "Publish Changes"
Visibility rules only take effect after publishing
Check User Role: Verify the user has the expected role assigned
Navigate to your Users table
Check the "Role" field for the affected user
Use "View as user" feature to test from their perspective
Multiple Conditions: When multiple visibility rules are set, ALL conditions must be met
Review each visibility condition on the page
Consider if any condition might be excluding the page unintentionally
Parent Page/Folder Visibility: If a page is in a folder, the folder must also be visible
Check visibility rules on parent folders
Ensure parent pages aren't hidden from the user role
Form Pages Not Appearing in Public Access
If your public forms aren't visible despite setting visibility to "Yes":
Public Access Setup: Ensure public access is properly configured
Go to Settings > Public Access
Verify the main toggle is enabled
Check that your app has been published
Table Permissions: The underlying table must allow public access
Go to Data & API tab > hover over table > Permissions
Create a permission rule for public users
Grant necessary field permissions (Create, Read as minimum for forms)
Page-Level Settings: Set the page visibility to Public
Select the form page in build mode
In the Visibility tab, select "All User types" or configure custom rules
Use the globe icon to explicitly mark as Public if available
Form Configuration: Verify the form itself is properly configured
Check that all required fields are visible
Ensure form submission is enabled
Test form submission in an incognito browser window
Frequently Asked Questions
Why can't I find the main menu to change user permissions?
Location of Visibility Settings:
Page Visibility:
Select page from sidebar > Enter build mode (Cmd/Ctrl + E) > Visibility tab
User Permissions:
Go to Settings > Users & Permissions or Data & API tab for table permissions
Component Visibility:
Navigate to record page > Build mode > Select component > Visibility tab
How do I fix conflicting visibility rules?
If you're getting notifications about conflicting visibility rules:
Review All Conditions: Check every visibility condition set on the page
Simplify Rules: Start with basic rules (like User Role only) and add complexity gradually
Test Incrementally: Use "View as user" after each rule change
Clear and Recreate: If rules are broken, delete all conditions and start fresh
Can I set different homepages for different user roles?
Yes, using page visibility and ordering:
Arrange Pages: Order pages in your sidebar with role-specific pages at the top
Set Visibility: Make the first page visible only to specific roles
Cascade Logic: The first visible page becomes the homepage for each user role
Test Roles: Use "View as user" to verify different homepages per role
Why do 'My Profile & Preferences' pages not show after onboarding?
This usually happens when visibility conditions are too restrictive:
Check Onboarding Filters: Remove any conditional filters from essential pages temporarily
Verify User Data: Ensure the user has all required field values populated
Review Custom Rules: Check if custom visibility rules depend on fields that might be empty
Test User Journey: Walk through the complete onboarding process using "View as user"
How do I create separate apps for different user types?
To create trade and client apps with different access:
Duplicate App: Create multiple apps connected to the same data source
Different Roles: Set up distinct user roles in each app
Separate Permissions: Configure different table permissions for each app
Custom Views: Create role-specific views and pages in each app
Public Access: Configure different public access rules if needed
What's the difference between page visibility and permissions?
Page Visibility: Controls what users see in the UI - pages, components, buttons
Set in build mode > Visibility tab
UI-level control only
Not secure (data still accessible via developer tools)
Permissions: Controls actual data access at the API level
Set in Data & API tab > Table permissions
Secure data access control
Prevents unauthorized data access entirely
Use Both: Combine visibility (good UX) with permissions (security) for complete access control.
Last updated
Was this helpful?