Skip to content
Data & security

Clear boundaries instead of inflated security claims.

OVL permissions, WordPress authentication and the site’s hosting/security configuration work together. This frontend does not change platform data or permission rules.

Venue separation

Venue-based records

OVL Core is responsible for ensuring users work inside the venue workspaces they are attached to.

Permissions

Role-based access

Owners, managers and staff can have different permissions. The public frontend does not grant or expand those permissions.

Authentication

Email + personal PIN

When Property Governance is active, OVL can use invitation-based email + PIN sign-in with hashed PIN storage and secure reset links. WordPress remains the underlying account/session system.

Subscriptions

MemberPress/Core flow

The public pages link into the existing subscription flow; they do not create a second billing system or write venue ownership directly.

Hosting

Infrastructure responsibilities

Backups, firewalling, server security and disaster recovery depend on the hosting and security services actually configured around WordPress.

Questions

Need a specific answer?

Use Contact & Support with the feature and use case so the response can be specific rather than generic.