> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Architecture and data flow

> Map Entelligence source connectors, processing, shared engineering context, model providers, destinations, analytics, and write actions.

Entelligence connects authorized engineering systems to product workflows and configured destinations. The exact data path depends on the product, connector, provider credentials, and deployment agreement.

## Verified product surfaces

The current app separates:

* **Connectors** for AI analytics, product analytics, communication, support, meetings, documentation, project management, observability, and CI/CD
* **Settings → Auth** for source-control authentication
* **Settings → Team** for members and AI-tool or work-system mappings
* **Settings → Code Management** for repository synchronization and repository-level controls
* Product settings for review, analytics, automations, and delivery
* **Settings → API** for CLI and MCP credentials
* **Settings → Slack Notification** for Slack delivery

<Frame>
  <img src="https://mintcdn.com/entelligence-c3217b42/vKFIv5-IGbQf-G8O/images/enterprise/code-review-settings.png?fit=max&auto=format&n=vKFIv5-IGbQf-G8O&q=85&s=e3170e14682603db5e6a77db3db87f6c" alt="Entelligence Code Review Settings showing review configuration, guidelines, learnings, and codebase context tabs" width="3024" height="1964" data-path="images/enterprise/code-review-settings.png" />
</Frame>

<Note>
  A connector card proves only that the integration is presented in the current catalog. Connection state, plan availability, permission scope, and supported actions must be checked in the workspace.
</Note>

## Build a workflow inventory

For each workflow, record:

| Field                | Example                                                                |
| -------------------- | ---------------------------------------------------------------------- |
| Source               | An approved repository, connector, or local agent source               |
| Data read            | Diff, repository context, event, ticket, message, or metric            |
| Entelligence product | Code Review, Agent Insights, Ask Ellie, or another enabled product     |
| Model path           | Hosted, BYOK, or another approved path shown for the deployment        |
| Stored output        | Review, generated content, mapping, incident, or analytics metadata    |
| Destination          | Pull request, Slack channel, dashboard, ticket, document, or client    |
| Write                | Comment, status, fix, ticket, message, export, or configuration change |
| Owner                | Named business and technical owner                                     |
| Retention            | Approved contract or policy value                                      |
| Region               | Approved contract value                                                |
| Revocation           | Provider removal, repository disablement, key rotation, or disconnect  |

## Separate reads from writes

<CardGroup cols={2}>
  <Card title="Read path" icon="book-open-reader">
    Inventory sources, fields, scopes, caches, derived metrics, model calls, and stored outputs.
  </Card>

  <Card title="Write path" icon="pen-to-square">
    Inventory comments, statuses, fixes, tickets, Slack messages, exports, credential changes, and billing actions.
  </Card>
</CardGroup>

Provider-side permissions remain the final access boundary. Test required writes with a reversible pilot, record the destination, and verify rollback.

## Shared context

Entelligence products can use authorized repository guidance, review feedback, incidents, delivery data, mappings, and agent analytics. Do not assume that all connected data is automatically shared with every product. Verify each product's configured sources and boundaries.

Cross-repository or cross-organization context requires explicit approval.

## Next step

Define [identity and permissions](/enterprise/permissions) and [privacy requirements](/enterprise/privacy).