Embedded Chat Sharing
Ragty can publish a chat dialog on third-party websites and applications through a share. This page describes the platform side: creating and operating shares as a Ragty administrator.
Concepts
Public | Delegated | |
|---|---|---|
Use case | FAQ, product documentation, help pages | Customer portals, online banking, logged-in areas |
User | Anonymous browser (no user is passed) | Verified end user ( |
History | Same device | Every device of the user |
Documents | Unowned documents only | The user's own plus unowned documents |
Requires | — | Delegated end-user isolation, trusted issuer, gateway key |
Integration types per share: web component (<m8ty-chat>, native in the host page) and/or iframe (isolated on the Ragty origin).
Create a share
Open Chat shares in the sidebar, or Chat → Settings → Sharing of a dialog. Tenant editors manage public shares; delegated shares require a tenant admin.
Click New share and set mode, integration type(s), the exact allowed origins of the integrator's pages (one per line, no paths, no wildcards), retention, messages per day, maximum characters per message and an optional expiry date. Delegated shares additionally need the trusted issuer and the gateway key the integrator's backend uses.
Save. The integration guide opens with copy-ready snippets (iframe, web component, JavaScript, TypeScript, Java, CSP). Hand the share ID, the Ragty base URL and — for delegated shares — the gateway key (via your secret process) to the integrator, together with a link to Chat Integration for Third-Party Applications.
For delegated shares also make sure that:
the integrator's identity provider is registered as a trusted end-user issuer for the tenant (see Delegated End-User Isolation), and
the JWKS host is on the outbound allowlist (see Outbound Egress Security).
Operate shares
Action (Chat shares page) | Effect |
|---|---|
Edit | Change name, origins, integration types, quotas, retention, expiry; removed origins take effect immediately |
Disable / Enable | Chat stops immediately everywhere; histories are kept |
End all sessions | Every open chat must re-authenticate (e.g. after suspected misuse) |
Delete chat histories | Deletes all chats of the share; the share stays active |
Delete | Deletes the share, its chats and visitor data permanently |
The list shows status (Active, Disabled, Expired, Gateway key invalid), integration types, origins, number of users and chats, and the last use. Every administrative action is recorded in the share's audit trail.
Automatic behavior:
Histories older than the retention period (since last activity) are deleted hourly; inactive anonymous visitors as well.
A revoked or expired gateway key disables its delegated shares (status Gateway key invalid); assign a new key to re-enable.
Deleting a chat dialog deletes its shares.
Erasing a delegated subject also erases their chat histories.
Platform configuration
Variable | Default | Purpose |
|---|---|---|
|
| Lifetime of a chat session token |
|
| Lifetime of a delegated one-time ticket |
|
| Maximum age of a request signature |
|
| Requests per visitor/user and minute |
|
| Requests per client IP, share and minute |
|
| New anonymous visitors per client IP, share and hour |
Routing: expose /embed/* and /embed-assets/* of the Ragty frontend through the public ingress (the frontend proxies /embed/v1/* to the backend), and /api/v1/embed/tickets of the backend for integrator backends.