Security & trust
Ozer Commercial property is built for agencies that care where client and instruction data lives.
At a glance
- Access to workspace data is enforced with Postgres row-level security (RLS) — members only see their account’s data
- Auth and billing use established providers (for example Supabase Auth and Stripe)
- Commercial portal credentials (Property Hive, Rightmove, EACH / EG) are stored for the workspace and must stay out of tickets and shareable docs
- Support seats are limited by design so viewers cannot change stages, disposals, or publishing
Steps for a secure desk
- Invite colleagues only from Team (
/app/[account]/members) with the correct seat kind. - Prefer support seats for people who only need visibility.
- Rotate Property Hive feed tokens from Website & portals if a URL may have leaked, then update Property Hive Import immediately.
- Avoid pasting portal secrets into chat, email signatures, or public boards.
- Keep private listing media on the disposal Management private media section, not on public Media.
- Review members when staff leave — remove memberships that should no longer access instructions.
Read more
Full trust and security overview: ozer.so/trust .
Last updated on