Skip to main content

General & Authentication

The General and Authentication tabs contain the core assistant configuration and integration settings.

General Tab​

General Settings

Basic Settings​

FieldDescription
Assistant Name *Display name shown on the chat widget (max 30 characters)
Greeting Message *Welcome message shown to users when they open the assistant
AvatarUpload a custom avatar image (PNG, JPG, WebP, max 5 MB, resized to 200x200px)
DomainThe domain where the assistant will be deployed
Sidebar BrandingCustom branding text displayed vertically in the chat sidebar (max 100 characters)

User Resolution​

FieldDescription
Default RoleFallback role used when user resolution fails or returns no matching role
User Resolver Webhook URLWebhook endpoint for identifying users from your authentication system
User Resolver Timeout (ms)Maximum wait time for the webhook response (1000--30000 ms)

See User Resolution for implementation details.

API Key​

The General tab also provides an API key for this assistant:

  • Generate or regenerate the API key
  • Copy the key to clipboard
  • Use this key when embedding the assistant in your application

Integration Guide​

A read-only section showing how to embed the assistant:

  1. Add the script tag to your HTML
  2. Add the web component
  3. Optional configuration parameters

Authentication Tab​

Authentication Settings

User Identity Resolver (BYOA)​

Configure the webhook that resolves user identity from your authentication system.

SettingDescription
Webhook URLPOST endpoint that receives auth headers (prefixed with X-User-Auth-) and returns user identity
Timeout (milliseconds)Maximum wait time for the webhook response (1000--30000 ms)

How it works​

The Authentication tab includes an explanation of the BYOA (Bring Your Own Auth) flow:

  1. Client sends auth headers (Authorization, Cookie, etc.) to your assistant
  2. Diosc forwards these headers to your webhook with the X-User-Auth- prefix
  3. Your webhook validates the auth and returns user identity
  4. Diosc uses the returned user info for personalization and access control

The expected webhook response format is shown in the tab:

{
  "userId": "user123",
  "displayName": "John Doe",
  "roles": ["user", "admin"],
  "email": "john@example.com",
  "metadata": {}
}

CORS Configuration​

SettingDescription
Allowed OriginsList of origins permitted to embed the assistant
Allowed HeadersHeaders forwarded from the client (add common headers with one click)

Next Steps​