> ## Documentation Index
> Fetch the complete documentation index at: https://help.casaconect.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Access control and tenant isolation
> How Casa Conect decides who can see what: organizations, roles, projects, per-document permissions, and the layers that keep one customer's data away from another's.
Every request to Casa Conect is answered by the same question: *who is asking, on behalf of which organization, and are they allowed to do this?* The answer always comes from a verified token and the server's own records, never from what the browser claims.
## Layers of access
The request must carry a valid sign-in token. See [Authentication](/security/authentication).
The token names the organization the person is working in, along with their **role** there. Both come from the identity provider, which is the system of record for memberships.
Administrative operations require the **Admin** role: inviting and removing members, changing roles, billing, organization settings, agent inbox configuration, and sharing templates with the organization.
Casa Conect OS features (the agent, matters, the editor and the agent inbox) additionally require that the organization has the product enabled and a subscription in good standing.
Finally the specific record is checked: is this person a member of the project? Can they see this matter? Do they hold a permission on this document type in this Shared Space?
## Roles
Casa Conect has two organization roles. For a full breakdown, see [Roles and permissions](/admin/roles-and-permissions).
| Role | In short |
| :--------- | :-------------------------------------------------------------------------------------------------- |
| **Member** | Does the work. Sees organization-wide content and the projects they belong to. |
| **Admin** | Everything a member can do, plus managing people, billing, policies and organization-wide settings. |
## Scopes of content
| Scope | Who can see it |
| :------------------------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Personal vault** | Only you. Not admins, not the agent on anyone else's behalf. |
| **Organization vault** | Members of the organization |
| **Project** | Organization-wide projects: every member. Private projects: the project's members and organization admins. They are hidden from everyone else, including their linked conversations. |
| **Conversation with the agent** | Private conversations: only the person who started them. Shared conversations: people who can see the project they belong to. |
| **Matter** | Follows its project, or the organization if it has none |
| **Shared Space** | Members of the space, further limited per document type and per summary category. See [Members and teams](/shared-spaces/members-and-teams). |
| **Share link** | Whoever holds the link and passes its checks. Not tied to an account. See [Share links](/shared-spaces/share-links). |
## Tenant isolation
Casa Conect is a multi-tenant service. Customers share infrastructure, and isolation is enforced in software at several independent layers:
* **Every data operation is scoped** by the organization and user taken from the verified token. There is no code path in which a client supplies an organization identifier and is simply believed.
* **The database schema itself enforces tenancy.** Records are tied to their organization in a way the database refuses to violate, even if application code contained a bug.
* **Search resolves access before it searches.** Document search first works out exactly which documents the person may read, and only then runs the search inside that set. See [Search](/documents/search).
* **Files are private by default.** Storage is never public, and every file access goes through a short-lived signed link issued after an authorization check.
## The agent's access
The agent has **no access of its own**. A session acts as the specific person who started it, with that person's role and project memberships. Every tool call passes through the same authorization as a click in the interface. For email from a verified member, the agent acts as that member. For an allowed external sender, it acts as the organization's agent with a deliberately small set of abilities. See [Agent safety](/security/agent-safety).
## Public share pages
Share links give outside parties narrow access without an account. A recipient is authenticated by their **share session**, not as a user, and that session grants nothing beyond the one link. Share pages have their own rate limits, and PIN attempts are refused outright if the limiter is unavailable.
## What admins can and cannot see
Organization admins can see and manage **every project** in the organization, including private ones, along with the matters and shared conversations inside them. This lets an admin step in when a colleague is away or leaves.
Admins **cannot** open a member's **personal vault** or a member's **private conversations** with the agent. Those belong to the individual.
This page describes our security practices at the level of a help page. We share detailed security documentation, architecture reviews and completed questionnaires with customers on request. Write to [support@casaconect.ai](mailto:support@casaconect.ai).