Softr client portal: connect records and check client access

Start with the data and access rule

Thanks to Softr for sponsoring this video.

The portal contains projects, invoices and requests. Northstar and Atlas are fictional clients, and the amounts are demonstration data. The intended rule is that a client sees records matching that client’s logged-in email.

The walkthrough includes blank panels that needed fixing. A convincing generated layout is only the starting point; its panels must read the connected tables and apply the intended filters.

Build and repair the portal

Use the chapter links to follow the actual build and the changes made when panels were empty. This checklist describes the demonstrated route rather than a complete database schema.

1. Plan the read-only client portal and its projects, invoices and requests.
2. Create the interface with the Vibe Coding Block.
3. Connect the database tables to the panels.
4. Match each record’s client email to the logged-in user.
5. Fix blank panels before refining totals, ordering and empty states.

Inspect different users

In Preview, compare Northstar, Atlas and a user with no assigned records. Check the actual lists and figures, not just whether the page loads. The no-records user should show an appropriate empty state.

These are checks of specific client views in Softr Preview. They do not constitute a complete security audit of a published application or prove that a different app has the same access behaviour.

The takeaway

Use fictional records to test each intended client view before considering real client information. Preserve the distinction between Preview checks and a security audit.