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

What is Public Access?

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.

How to Enable Public Access

You can configure public access in any app — new or existing — in just a few steps:

1. Open your app settings and select Public Access.

2. Click Setup to begin configuration (your app won’t go live yet).

3. Expand the table list to choose which tables should be available publicly.

4. Toggle public access on for selected tables.

5. Use the Permissions Panel to define exactly which fields and records are public. Learn more about permissions

6. In the Views Tab, choose which views are publicly visible. Learn more about visibility rules

7. Set your navbar pages to be Public, Shared (conditionally visible), or Private.

8. When ready, toggle the main switch to enable public access.

9. Click Review & Publish to finalize and make your app publicly accessible. Learn more about publishing

🔒 By default, everything is private. You have full control

Best Practices for Safe & Effective Public Access Apps

• 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.

Security & Limitations

• Public data is fully accessible without login, but you control what’s exposed.

• Use field- and record-level permissions to ensure data safety.

• 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.

Frequently Asked Questions about Public Access

Is my data safe if I enable Public Access?

Yes. Only the data you explicitly mark as public is exposed.

Can people see all of my tables and fields?

No — you control which are visible using permissions.

Can public users submit forms or edit records?

Yes, but only if you enable those features by defining specific permission rules for pubilc users

Can I personalize the app for each visitor?

Only for logged-in users. Public visitors see general content only.

Troubleshooting

I turned on public access, but users still need to log in.

Make sure the pages and tables are explicitly set as public in your settings, and that you have published your app

My data isn’t showing on public views.

Check that you’ve selected views in the Views tab and that permissions allow public visibility.

Some fields are missing on public pages.

Review your field-level permissions — they may be restricted for public users.