Connect the account and select a project
- 1
Open Data → Databases
Open a saved Unbondr project with database access (Pro) and permission to edit. Choose Connect Supabase account. Authorize access using a Supabase account that can see the intended project.
- 2
Choose Use this project
Select the active Supabase project. The connection identifies the remote project. Each data source on that connection defines a particular table query or a set of visitor authentication controls.
- 3
Choose a source mode
Select Table data and forms to read records. Select Authentication only for visitor login and registration without creating an application table. Give each source a stable key, such as posts or account.
Prepare a public read policy
For a minimal working example, run the following once in the SQL Editor of a test project with an unused public.docs_posts table name. It creates one published row and one draft. Anonymous and signed-in visitors can select the published row. The example grants read access only.
begin;
create table public.docs_posts (
id integer primary key,
title text not null,
href text not null,
published boolean not null default false
);
alter table public.docs_posts enable row level security;
revoke all on public.docs_posts from public, anon, authenticated;
grant select on public.docs_posts to anon, authenticated;
create policy "Read published posts" on public.docs_posts
for select to anon, authenticated using (published is true);
insert into public.docs_posts values
(1, 'Release notes', '/releases', true),
(2, 'Draft announcement', '/draft', false);
commit;Validate the read plan
- 1
Select the table and output columns
Choose docs_posts, use posts as the source key, and select id, title and href. Choose public access. For repeatable ordering choose id as the sort column. Set a row limit between 1 and 100.
- 2
Save and inspect Public sample
Review the publishing consent and choose Validate and add source. With the example policy, the public sample should contain Release notes. Save later edits with Validate and save source.
- 3
Choose private access where needed
For account-specific data choose authenticated access and configure the table’s SELECT policy for the signed-in user. The canvas uses saved public samples. Test private reads in the generated application with a visitor account.
[{"column":"published","value":true}]