> ## 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.

# Enterprise deployment and trust

> Plan Entelligence identity, connectors, deployment, data boundaries, roles, credentials, networking, rollout, and procurement.

Enterprise review should separate three kinds of evidence:

1. Product behavior visible in the current Entelligence app
2. Public statements published by Entelligence
3. Contractual commitments in your security package, DPA, order form, or support agreement

## Verified public and product evidence

<CardGroup cols={2}>
  <Card title="SOC 2 Type II" icon="badge-check" href="https://entelligence.ai/">
    The current public homepage states SOC 2 Type II. Request the current report, audit period, system scope, exceptions, and bridge letter.
  </Card>

  <Card title="Privacy policy" icon="file-shield" href="https://entelligence.ai/privacy-policy">
    Review the published policy for personal-data processing, U.S. transfers, retention language, and privacy contact details.
  </Card>

  <Card title="Workspace controls" icon="user-shield" href="/administration/overview">
    The audited app exposes Member/Admin roles, provider authentication, repository controls, API keys, billing, and Slack delivery.
  </Card>

  <Card title="Security package" icon="folder-lock" href="mailto:support@entelligence.ai?subject=Enterprise%20security%20package">
    Request the documents and deployment commitments that are not established by the UI or public website.
  </Card>
</CardGroup>

<Info>
  A badge or public statement is not a substitute for the underlying report. Confirm the audited boundary, period, complementary customer controls, exceptions, and whether your purchased deployment and products are in scope.
</Info>

## Evaluation workstreams

| Workstream   | Verify in the app                                                         | Confirm in approved documents                                               |
| ------------ | ------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Architecture | Connected sources, configured products, destinations, and write controls  | Network diagram, processing boundaries, storage, and model-provider path    |
| Identity     | Member/Admin behavior, provider scope, mappings, keys, and offboarding    | SSO, SCIM, MFA, session, support-access, and audit commitments              |
| Privacy      | Visible data sources, generated outputs, and deletion/revocation behavior | Retention, deletion, residency, subprocessors, training, and backup terms   |
| Deployment   | Hosted application and client connectivity                                | Alternative deployment options, responsibility split, recovery, and support |
| Reliability  | Product health, retry behavior, and rollback tests                        | Availability, incident notification, RTO/RPO, and maintenance commitments   |
| Compliance   | Public SOC 2 Type II statement                                            | Current report, bridge letter, scope, exceptions, and remediation           |

## Recommended evaluation

1. Choose one measurable use case.
2. Connect one source with minimum scope.
3. Use an Admin and a normal Member test account.
4. Verify a read-only result.
5. Test one reversible write only when required.
6. Record access, audit, rollback, and deletion evidence.
7. Pilot with a small group.
8. Review product value and operational burden.
9. Expand repositories, teams, and actions in stages.
10. Revalidate after a connector, model, deployment, or policy change.

## Do not infer from the UI

The current settings audit does not establish contractual behavior for SSO/SAML, SCIM, data residency, exact retention, immutable audit logs, model-provider terms, availability, recovery, support access, packaging, or price.

## Next step

Start with [architecture and data flow](/enterprise/architecture), then use the [administrator checklist](/get-started/admin-checklist).