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

# Tenant and account isolation

> Keep repository identity, tenant authorization, and vendor account authority aligned.

EyeParity is a multi-tenant platform. Tenant data, workplans, proof artifacts, and control-plane operations require authenticated authorization for the intended tenant. A session that is valid for one product is not automatically valid for another.

## Repository-first authorization

Before a repository-scoped integration call:

1. determine the canonical target repository;
2. resolve the account authority assigned to that repository;
3. verify the authenticated session matches the resolved authority;
4. limit the operation to the resolved deployment and tenant;
5. fail closed on any mismatch.

For Mintlify operations, EyeParity uses its dedicated owner and MCP selector. A support identity is not a fallback reader or administrator for EyeParity.

## Read operations are security-sensitive

Cross-tenant isolation applies to inventory and search calls as well as writes. A read-only query can still disclose deployment names, navigation, member information, analytics, or unpublished content.

## Evidence without secrets

Record non-secret authority facts such as the repository, authority source, MCP selector, deployment selector, and pass/fail outcome. Never include passwords, OAuth codes, tokens, cookies, or credential values in documentation, workplans, logs, or screenshots.

<Warning>
  If the owner, selector, tenant, or deployment does not match the target repository, stop before the vendor call and re-establish the correct authenticated session.
</Warning>