Resources

Company

Support data deserves strict boundaries.

Envelen keeps authorisation on the server, customer identity verifiable, integrations scoped, and AI behind explicit policy and human review.

Workspace and application boundaries

Authorisation is enforced at server-side boundaries. Workspace membership, role, application scope, and conversation access are checked before data is read or changed.

A client-supplied workspace or application identifier is never treated as permission on its own.

  • Tenant-scoped queries
  • Role-aware dashboard actions
  • Application-scoped widget sessions
  • Audit history for sensitive operations

Verified customer identity

Authenticated products issue a short-lived support token on the server. The widget uses that token to connect a customer to the intended application without trusting a browser-supplied user ID or email.

Anonymous sessions are bounded by the application's registered origins and server-side session policy.

Scoped integrations and secrets

Public API access uses scoped keys. Webhook deliveries are HMAC-signed and designed for bounded retry and durable attempt history. AI provider keys are encrypted at rest and are not returned to the browser after configuration.

Secrets belong in server-side environment or encrypted configuration, never in widget code or public documentation.

Files and Knowledge content

Customer and Knowledge uploads are limited to supported image formats, validated by content signature, stored privately, and served through authenticated short-lived access. Customer attachments remain disabled by default per application.

Published and internal Knowledge retain separate visibility rules. Customer-facing AI can retrieve only content explicitly published for that use.

AI fails closed

Copilot receives policy, verified context, conversation history, and authorised Knowledge as distinct inputs. Structured output is validated before a suggestion is stored, and provider or validation failures do not create a customer-visible message.

The current beta requires human review before send. BYOK changes who pays the provider; it does not bypass Envelen's policy, authorisation, rate limiting, or audit controls.

Current assurance

This page describes implemented product boundaries, not an external compliance certification. Envelen does not claim SOC 2, ISO 27001, HIPAA, or another certification here.

Security and privacy documentation will be updated as hosting, billing, retention controls, and external assurance mature toward general availability.

Next step

Put the support loop into practice.