Integrations
Alcilla.Desk is designed so that additional systems can be connected selectively. Not every integration is required for every company. The actual scope is configured to suit the use case.
Overview
| Area | Supported or planned connection |
|---|---|
| AI models | Ollama and other compatible model endpoints |
| IMAP for receipt and synchronization, SMTP for sending | |
| Calendars and tasks | CalDAV and ICS sources |
| Documents | Local or provided folders, conversion through Docling |
| Web research | SearXNG and publicly accessible websites |
| Time tracking | Kimai or Clockify, depending on the configuration |
| Sign-in | OIDC-compatible identity provider |
| Shared knowledge | Central Alcilla.Desk service |
Existing email accounts can be connected through IMAP and SMTP. Before introduction, the following should be reviewed, among other things:
- the supported authentication method,
- TLS configuration,
- folder structure,
- size of the existing mailbox,
- policies for local storage,
- handling and retention of attachments.
Calendars and tasks
CalDAV can be used for calendars and task lists. ICS feeds can additionally serve as appointment sources.
Because CalDAV providers implement functions differently, the specific target environment must be tested.
Enterprise sign-in
In centralized operation, Alcilla.Desk can be connected to an identity provider through OIDC. Group information can be used for administrative permissions and approvals.
Documents and file storage
Alcilla.Desk can add defined document folders to the knowledge index. A processed text version is created for Word, PDF, and similar formats.
When selecting folders, the following are particularly important:
- subject-matter responsibility,
- currency of the content,
- duplicates,
- access permissions,
- confidential or excluded areas,
- lifecycle and deletion.
Web search
SearXNG serves as the upstream search component for research. Depending on security requirements, it can be operated internally and restricted to permitted search sources.
Model endpoints
Alcilla.Desk can use different models for different tasks. For example, a local model can process confidential content while another internal endpoint handles compute-intensive tasks.
Not familiar with Ollama or Docker yet? That is not a barrier. We can build the technical setup, guide your IT team, or define a jointly managed operating model.