Domain Configuration

Domains define where Appilot is active. The assistant only provides knowledge-grounded answers on domains your organization has registered and configured.

Registering a domain

1. Go to Domains in the Backoffice
2. Click Register Domain
3. Enter the domain (e.g., app.example.com)
4. Optionally add URL patterns for specific pages
5. Save

URL patterns

URL patterns control how knowledge is matched to pages:

Pattern	Matches
/register	Exactly app.example.com/register
/settings/*	Any page under /settings/
/forms/claim-*	Pages like /forms/claim-auto, /forms/claim-health
*	Any page on the domain

Domain harvesting

Before you register domains manually, check the Harvested Domains section. Appilot automatically tracks which domains your extension users visit:

• See domains ranked by visit frequency
• Identify which web apps your team uses most
• Register harvested domains with one click

This is especially useful during initial rollout — install the extension, let users work normally for a week, then register the most-visited domains.

Managing domains

For each registered domain, you can:

• View associated knowledge content
• See user activity and question volume
• Upload RAG files specific to this domain
• View and manage URL patterns

Applications

Domains can be grouped into Applications — logical units that represent a web application:

• An application might have multiple domains (e.g., app.example.com and api.example.com)
• Knowledge and files can be associated at the application level
• Analytics can be viewed per application

Site Adapter Configuration

For applications that use non-standard web frameworks (like Vaadin, which uses Shadow DOM and doesn't change URLs during navigation), you can configure a Site Adapter per domain.

What Site Adapters Do

A Site Adapter is a JSON configuration that tells the Appilot extension how to behave on a specific domain:

• Shadow DOM Depth: How deep to traverse Shadow DOM trees (default: 3, increase for frameworks like Vaadin)
• Page Detection: Rules to identify which page/module the user is on, using DOM selectors instead of URLs
• Interaction Overrides: Custom strategies for interacting with framework-specific components (e.g., Vaadin combo boxes)
• Knowledge Hints: Whether to match knowledge by module/page keys instead of URL patterns

Configuring an Adapter

1. Navigate to Apps → select your application
2. In the domains table, click the gear icon (⚙) next to the domain
3. Edit the JSON configuration in the modal
4. Click Save Adapter Config

Example: Vaadin Application

{
  "schema_version": "1.0",
  "domain": "your-app.example.com",
  "framework_hints": ["vaadin"],
  "runtime": {
    "shadow_dom_max_depth": 6,
    "action_timeout_ms": 3000,
    "mutation_observer_debounce_ms": 500
  },
  "page_detection": {
    "strategy": "dom_selector",
    "rules": [
      {
        "selector": "vaadin-menu-bar [selected]",
        "read": "innerText",
        "map": {
          "Online Services": { "view_path": "app/online-services" },
          "Organizations": { "view_path": "app/org-units" }
        }
      }
    ]
  },
  "interaction_overrides": {
    "vaadin-combo-box": {
      "strategy": "open_then_select",
      "open_trigger": "click",
      "option_container_selector": "vaadin-combo-box-overlay [part='item']"
    }
  },
  "knowledge_hints": {
    "always_include_scopes": ["domain_global"]
  }
}

tip

For standard web applications where URL changes reflect navigation, you don't need a Site Adapter. The default behavior works well for most SPAs and traditional websites.