01
Tenant isolation by construction
Every tenant-owned row carries its workspace. PostgreSQL row-level security denies access by default, and the application runs tenant queries through a restricted database role.
Security
Security built into every customer conversation.
Customer conversations contain sensitive information. InboxLapp limits access with tenant isolation, server-side authorization, granular roles, and audit history.
Available nowInboxLapp
One connected customer workspace
At a glance
- Workspace isolation
- Server-side authorization
- Audit history
Start with live chat and a shared inbox today. Add AI, knowledge, and automation as they become available for your workspace.
02
Authorization is enforced on the server
Roles and permissions are evaluated for every sensitive request. Hiding a button in the interface is never treated as a security boundary.
03
Sessions and auditability
Session tokens are opaque and stored as hashes. Security-relevant changes record the actor, action, target, and timestamp so access can be reviewed later.
Common questions
Good to know.
Straight answers about setup, data, and what is available today.
Where does customer data live?
Every workspace is isolated with PostgreSQL row-level security and server-side authorization. Session tokens are opaque and hashed, and security-relevant changes are recorded in the audit trail.
Is data encrypted in transit?
Production deployments require HTTPS and a TLS connection to managed PostgreSQL. The application refuses to start in production without an HTTPS APP_URL.
Can I control what each teammate sees?
Yes. Workspace roles and granular permissions are checked on the server, and property-level access can keep customer conversations scoped to the right team.
Keep exploring
Bring every customer conversation into one place.
Start with live chat. Add the rest as your team grows.