How your company's data is kept separate

Each company's data lives in its own workspace. Northwind Oy's documents, memory, chats, tasks, agents, and connections belong to Northwind Oy's workspace and are never visible from another company's workspace.

Two layers of protection

Every piece of company data is stored with the workspace it belongs to. CORA protects it in two independent ways:

1. Application checks. Every request checks who you are and which workspace you are working in before data is read or changed.
2. Database rules. The database itself enforces row-level security on company data, so a mistake in one part of the application still cannot reveal another workspace's rows.

Browsers and outside tools never query the database directly. Everything goes through CORA's own interfaces, which apply the same checks for the web app, the CORA apps for phone and desktop, and approved external assistants.

Roles stay inside their workspace

A role you hold in one workspace gives you no access in another. If you belong to several workspaces, CORA only uses the one you are working in. Work that waits in a queue checks your current membership and permissions again before it runs, so removing someone takes effect for work they started earlier too.

Separation inside a workspace

Isolation does not stop at the workspace boundary:

• Chats are private to the person who started them.
• Company roles set under Settings -> Roles & permissions can restrict knowledge, capabilities, and fields to the people who need them. Restricted content is filtered out before it reaches chat, agents, search, or exports.
• Project files and instructions are used only when someone works inside that Project.
• Personal workspaces are separate from company workspaces. A company has no access to a member's Personal workspace, and Personal data never mixes with company data.

Agents follow the same rules

Agents receive only the context the requesting person is allowed to see. Each agent has a fixed list of tools and actions it may use, and actions that change data follow the approval rules your administrators set.

Where it is stored

Stored workspace data stays in the EU in both processing packages. See Data residency: EU only and Flexible for details.