Role-based workspace access
Owner and staff permissions keep workspace, integration, finance, and configuration controls with the people expected to use them.
Security, privacy, and control
Flexboox makes access, data movement, exports, retention, and operational accountability visible—so a business can evaluate the controls available today before trusting the workflow.
Current product posture
Controls you can verify
Workspace access
Role and permission checks
Tenant boundary
Workspace-scoped records
Data portability
Admin JSON export
Operational history
Traceable high-impact actions
Verified in the current product: role-based access, tenant-scoped records, secret-redacted exports, and traceable high-impact actions.
Current safeguards
The useful question is who can do what, how sensitive actions are constrained, and whether the resulting activity can be reviewed.
Owner and staff permissions keep workspace, integration, finance, and configuration controls with the people expected to use them.
Operational records stay bound to a workspace so one business cannot browse another business’s bookings, customers, or configuration.
Important booking, payment, integration, support, export, and configuration activity is written to structured operational records.
Elevated platform access uses multifactor checks, explicit review, and privacy-aware operational views.
Support sessions require a documented purpose, recent authentication, a fixed expiry, and an audit record.
Configured Stripe or Mollie accounts handle payment collection while Flexboox keeps booking and payment status connected.
Data responsibility
A business chooses its calendars, payment providers, communication services, and external destinations. Flexboox keeps those routes explicit during setup.
01
The booking page collects the information required by the configured booking path.
02
Availability, eligibility, booking state, and owner-visible history remain tenant-scoped.
03
Only enabled calendars, payments, communication services, or external destinations receive their required data.
Provider availability and exact data handling depend on the workspace configuration and the provider account selected by the business.
Data controls
Export, retention, cancellation, and deletion are related—but they are not the same operation. The current product keeps those boundaries explicit.
Export
Authenticated workspace admins can download a tenant-scoped JSON export. Authentication, API, OAuth, invitation, management, and provider secrets are removed from the file.
Exports are rate-limited and recorded in the workspace audit history.
Retention
Workspace settings cover messages, provider events, analytics, operational and audit logs, invitations, client-record review, deletion markers, and backup-expiry targets.
A dry run shows eligible records without deleting tenant data; legal holds block destructive apply.
Leaving
Paid-plan cancellation is handled through billing management. Permanent workspace deletion is a scheduled, preflighted operation that also handles connected storage, credentials, billing, and authentication records.
Flexboox does not present workspace deletion as an instant self-service action today.
Evidence boundary
Current product controls
Roles, tenant-scoped access, audit records, limited support sessions, rate limits, secret-redacted exports, retention controls, guarded webhooks, and integration credential masking.
Operational evidence
Production-readiness checks, health routes, delivery ledgers, controlled retention runs, guarded webhook processing, and documented recovery actions.
Evidence scope
Security statements on this page describe current product controls. Formal certifications, independent audit coverage, hosting-region commitments, and uptime SLAs are documented only when they can be verified.
Recent product work
These are current product refinements, not a substitute for a formal release history.
Expanded the directory example to six providers with richer filters, list, map, and split views, plus a visible Rotterdam map.
Refined the read-only examples with authentic workflow data, current product states, and a clear explanation that demo interactions are not saved.
Tightened service, date, time, and mobile review states so the public example better represents the current booking experience.
Evaluate the product directly
Create a booking page without adding payment details, or inspect the interactive examples before registering.