Public Access
Public Acces let you share specific parts of your Noloco app with the world β no login required. Whether you're showcasing a course catalog, event listings, or a product directory, you stay in control
Last updated
Public Acces let you share specific parts of your Noloco app with the world β no login required. Whether you're showcasing a course catalog, event listings, or a product directory, you stay in control
Last updated
Public Access allow parts of your Noloco app to be accessed without a user logging in. You decide:
Which tables are visible
Which records and fields can be viewed
Which pages are public, private, or shared
This means you can create rich, read-only public content while still keeping sensitive or interactive features behind login.
Public Access is available on the Business and Enterprise plan.
You can configure public access in any app β new or existing β in just a few steps:
Open your app settings and select Public Access.
Click Setup to begin configuration (your app wonβt go live yet).
Expand the table list to choose which tables should be available publicly.
Toggle public access on for selected tables.
Use the Permissions Panel to define exactly which fields and records are public.
In the Views Tab, choose which views are publicly visible.
Set your navbar pages to be Public, Shared (conditionally visible), or Private.
When ready, toggle the main switch to enable public access.
Click Review & Publish to finalize and make your app publicly accessible.
π By default, everything is private. You have full control
Expose only necessary fields. Donβt make entire tables visible unless needed.
Use a dedicated permission rule for public users. This avoids overlap with logged-in users.
Create public-specific views. These can simplify layouts and avoid confusion.
Default to read-only access. Only allow updates or submissions when absolutely required.
Public data is fully accessible without login, but you control whatβs exposed.
Public views refresh less frequently than authenticated ones, which helps manage load.
Personalization (e.g. user-specific content) requires login and wonβt work in public view.
Existing apps can be partially opened up β keep secure sections fully private.
Use - and to ensure data safety.
No β you control which are visible using .
Yes, but only if you enable those features by defining specific for pubilc users
Make sure the pages and tables are explicitly set as public in your settings, and that you have
Review your β they may be restricted for public users.