In a shared space, control matters even moreIsolation and human-in-the-loop approvals, by design
When a whole team works with AI, secrets, documents and accounts need clear walls. Cora is built with them from the start.When people and agents share a workspace, secrets, documents and accounts need hard boundaries. Team Cora is built with them from the start.
Sent only to www.googleapis.com · added by Megan · never shown againCRM_API_TOKEN · Allowed
Sent only to the site Daniel named · never shown againCora uses a key without seeing it. She sees only its name.
Secrets the AI can use but never readCredentials never enter the model’s context
When Cora needs a secret key to reach your data, that key lives in a vault. It is used straight from the vault and sent only to the site you named. The AI never reads it.
Nobody can read a key back once it is saved, not even the person who added it. Ask first puts each use on an approval card for the mission’s admins.
Cora works in the cloud, not on your computerIsolated execution in the cloud, never on your devices
AI that runs on your own machine can reach the files, passwords and accounts on it. Cora runs in a sandbox in the cloud that belongs to your organisation. Each organisation has its own sandbox, walled off from every other team.
Your laptop: closed
Nothing is running on your device, and nothing on it is being read.
The sandbox has your organisation’s own folder and the public web. Keys and connections are used for Cora outside it, never inside. Commands in it run without an approval card, because a task can need dozens of them; anything that changes another system still waits for one.
Clear walls, everywhere
- You choose what is sharedEach mission has its own people, Artifacts, vault keys and the connections switched on for it. A personal connection stays personal unless its owner shares it.
- Away from your devicesCora cannot leak a secret, a document or an account that lives on someone’s laptop, because she never touches it.
- Walled offTenant isolationEach organisation’s sandbox is walled off from every other organisation’s, and from Team Cora’s own systems.
- Asks before it actsHuman-in-the-loop approvalsA tool set to Ask first waits on an approval card before it changes anything. An org admin sets this on organisation connections. A personal connection starts on Allowed, because adding it was its owner’s choice, and its owner can set any tool to Ask first.
- Private words stay privateAsk Cora to polish a message before you post it: the words you typed first are never stored.
- Keys out of the chatIf someone pastes a key in the chat, Cora will not use it. She asks for it to be added to the vault instead.
Work with AI, safelyRun agents, safely
Set the objective. Bring your people. Cora coordinates the rest.Set the objective. Bring your people. Cora orchestrates the agents.