Workspace isolation

STYD keeps workspaces separate. Each workspace works with its own connections, members, settings, usage, and configuration.

What isolation means here

A workspace does not reach into another workspace's connections or data. If you work across several workspaces, each one is its own space, which is why keeping them organised matters.

Before asking a question, confirm you are in the intended workspace. The selected workspace decides which connections and data your question uses.

Private chat threads

Isolation also applies within a workspace: chat threads are private by default. A thread is accessible only to the person who created it and to members they explicitly invite, and only while those members are still in the workspace. Workspace membership alone does not expose every thread, and this is enforced on the server.

Client Portal isolation

The Client Portal applies a similar principle for client companies: each client company sees only its own documents and messages, resolved on the server from the signed-in person's membership. One company does not see another's content.

A boundary inside STYD

Workspace and company isolation are boundaries within STYD. They work alongside, and not instead of, the database and Odoo permissions that protect the underlying data.