Getting Started

In a nutshell

What this document is: A high-level overview of how to deploy Clawscan within your environment.

Why this matters: Helps you understand the required components, responsibilities, and deployment steps before starting the installation.

When to use this: Initial onboarding, project planning, IT scoping.

---

Overview

Clawscan is deployed directly within your Microsoft 365 and Azure environment.

This ensures:

• full control over communication data
• no transfer of raw email content outside your tenant
• alignment with internal security and compliance requirements

See:

• Architecture Overview
• Data Flow Overview

---

What you need

Before starting, ensure you have:

• access to a Microsoft 365 tenant

• access to an Azure subscription

• permissions to create:

  • shared mailboxes
  • Azure resources
  • application registrations

Deployment typically involves both IT and compliance stakeholders.

---

Deployment steps

The setup follows four main steps:

1. Shared mailbox setup Provision the mailbox used to ingest communications.

2. Azure resource group creation Create the container for all Clawscan resources.

3. AI configuration Configure the AI environment used for analysis.

4. Clawscan Engine deployment Deploy the containerized engine within your Azure environment.

Each step is described in detail in:

• Deployment Guide

---

Roles and responsibilities

Clawscan follows a client-controlled deployment model:

• your organization deploys and controls the infrastructure
• Clawscan provides the software and control plane
• GOlegal does not access communication content

See:

• Shared Responsibility Model

---

What happens after deployment

Once deployed, you can:

• configure detection domains (e.g. competition law, anti-corruption)
• manage the system via the Admin Control Center
• monitor activity and review results

See:

• Configuration Guide
• Admin Guide