Clevermore Documentation

Technical documentation for IT teams deploying and managing Clevermore across your organization.

This documentation is intended for IT administrators and implementation partners. For end-user guidance, see the user docs.

What is Clevermore?

Clevermore is an AI-powered Microsoft Outlook add-in built for law firms. It runs as a taskpane inside Outlook, extracting actionable tasks, building a searchable knowledge wiki, and maintaining rich contact profiles — all from email content attorneys are already working with.

The platform is designed around the unique requirements of BigLaw: client-matter isolation, ethical walls, zero-retention AI processing, and flexible deployment models that range from fully managed to on-prem.

How Clevermore Connects to Azure

Clevermore is a web-based Office Add-in — not a COM/VSTO plugin. It consists of a manifest file (deployed by IT through the M365 Admin Center) and a web application (loaded into Outlook’s taskpane over HTTPS). There is nothing to install on individual workstations.

Azure organizes resources in a hierarchy of containers. The diagram below shows where Clevermore’s components live and how Outlook connects to your organization’s Azure tenant.

Layer	What It Is	Clevermore Usage
Azure AD Tenant	Identity boundary for your organization. Contains users, groups, and app registrations.	Admin consent grants Clevermore access. Users authenticate via SSO.
Microsoft 365	Productivity services (Outlook, Exchange) managed through the M365 Admin Center.	IT deploys the add-in manifest through the M365 Admin Center.
Subscription	Billing container for Azure resources. A tenant can have multiple subscriptions.	On-prem only — hosts the resource group containing Clevermore infrastructure.
Resource Group	Logical grouping of related Azure resources within a subscription.	One per deployment, containing PostgreSQL, Redis, Web PubSub, and Container App.

Authentication is seamless — Outlook provides an SSO token that Clevermore exchanges with Microsoft Entra ID via the On-Behalf-Of (OBO) flow. No separate Clevermore credentials are needed, and updates ship automatically when the web application is redeployed.

Centralized deployments only touch the top two layers — admin consent and manifest deployment. No Azure subscription or resource group is needed from the firm.

Deployment Options

Clevermore supports two deployment models on a continuum. Every firm starts with centralized hosting and can migrate to on-prem as needs evolve — the application architecture is identical in both modes.

Centralized — backend infrastructure runs in Clevermore’s Azure tenant. Fastest onboarding, no Azure subscription required from the firm.
On-prem — backend infrastructure runs in the firm’s own Azure tenant via Lighthouse delegation. Full data sovereignty with Clevermore managing operations remotely.

See Deployment Models for a detailed comparison, and Infrastructure for the Azure resources involved.

Documentation Map

Platform ArchitectureApplication layers, authentication model, data flow, real-time updates
Deployment ModelsCentralized vs on-prem, Lighthouse delegation, migration path
Infrastructure StackPostgreSQL, Redis, Web PubSub, Container Apps, security configuration
Onboarding FlowStep-by-step deployment walkthrough, from admin consent to verification