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

# Responsibilities

**Security in the cloud and on multi-tenant platforms:** responsibility is always shared. The table below makes explicit where Tess’s responsibility ends and the customer’s begins — avoiding ambiguous expectations in audits and day-to-day use.

## Shared model

| Topic                       | Tess responsibility                                                                                                                     | Customer responsibility                                                                                 |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Infrastructure and platform | Hosting, encryption, isolation between organizations, monitoring, vulnerability management, and incident response in the Tess perimeter | Networks, devices, and security of the environment from which your users access the service             |
| Workspace users             | Provide roles, invites, and permission controls in the product                                                                          | Invite, review, and remove users; apply least privilege inside your team                                |
| Authentication              | Protect platform login; offer SSO/MFA according to the plan and available configuration                                                 | Protect passwords and tokens; secure your Identity Provider when corporate SSO is in use                |
| Product configuration       | Secure defaults and governance features (roles, sharing, execution audit)                                                               | Define roles, agent/page visibility, integrations, and internal usage policies                          |
| Content sent to AI          | Process under contract, isolation, and privacy policy; do not train Tess’s own models with that content                                 | Ensure lawful basis, internal classification, and appropriateness of prompts, uploads, and publications |
| Incidents                   | Investigate and respond in the Tess perimeter; communicate according to severity and obligation                                         | Promptly notify suspicions involving accounts, credentials, or anomalous use in your organization       |

## Related

* [Identity and Access](/Identity-Access)
* [Tess Commitments](/Tess-Commitments)
* [Incident Response](/Incident-Response)
* [Privacy](/Privacy)