Harrow Bay

Overview

Datasets

Query console

Routines

Governance

Access rules 14

Member roles 6

Audit trail

Key rotation

Delivery

Object storage 92%

Edge routines

Webhooks

Usage & limits

Access rules

Row-scoped rules govern who may read or write each dataset.

Allow read for signed-in members

Grants read access to the Asset library dataset for any member holding a valid session token.

SELECT · PERMISSIVE

Restrict updates to record owners

Members may modify a row only when its member_id column matches their own identifier.

UPDATE · RESTRICTIVE

Block deletes on archived rows

Rows flagged as archived stay immutable until an operator lifts the retention hold.

DELETE · RESTRICTIVE

Crew roster lookup via definer

Joins the crews dataset through a security definer routine so the roster stays hidden.

ALL · PERMISSIVE

Create a new access rule

Rule Name

Allow insert for verified members

Dataset onclause

public.Asset library

Rule Behavior asclause

Permissive

Rule Operation forclause

Member Roles toclause

VERIFIED Search for a role

Use options above to edit

1create rule "Allow insert for verified members only"

2on "public"."Asset library"

3as PERMISSIVE

4for INSERT

5to verified

6with check (

7 true

8);

Templates

Search templates

SELECT

Allow read access for everyone

This rule grants read access to your dataset for every visitor through the SELECT operation.

INSERT

Allow insert for verified members only

This rule grants insert access to your dataset for verified members and nobody else.

DELETE

Allow delete scoped to member_id

This rule assumes your dataset carries a column called "member_id", and lets people remove rows whose "member_id" column matches their own ID

INSERT

Allow insert scoped to member_id

This rule assumes your dataset carries a column called "member_id", and lets people add rows whose "member_id" column matches their own ID

UPDATE

Rule with dataset joins

Query across datasets to build sharper access rules

Assuming 2 datasets called crews and rosters, you can query both datasets in the rule to govern access to the rosters dataset.

ALL

Rule with security definer routines

Useful in a many-to-many relationship where you want to restrict access to the linking dataset.

Assuming 2 datasets called crews and rosters, a definer routine keeps the lookup out of the caller's reach.