Where your data lives in Sasha

Your own instance

Before you put your knowledge into Sasha, you need to know where it goes and who can reach it.

Each organisation has its own Sasha instance. No other organisation shares it. The instance runs in your organisation's own cloud account, or Context is Everything hosts it for your organisation. To find out which applies to you, ask your Sasha administrator.

What Sasha keeps in your instance

  • Your documents, grouped into projects. For how projects work, see How Sasha organises your knowledge into projects and documents.
  • Chats in the Sasha web interface. Admin and staff accounts chat with Sasha there, and Sasha keeps those chats. Members do not chat in the Sasha web interface.
  • Meeting records. When Sasha transcribes a meeting, Sasha writes the record as a document in the meetings folder of a project while the meeting runs.
  • App records. An app can keep its own records, apart from your documents. For apps, see Use and manage apps built on your knowledge.
  • Your connections. Sasha keeps a record of each Claude connection. Admin and staff accounts can see and remove their own connections in Sasha. Sasha also keeps a log of the requests that Claude makes through each connection, such as the words of a search, or the project and path of a document that Claude reads or writes. The log does not hold Sasha's answers or the text of documents that Claude writes.
  • Skill results. When someone runs a skill from Claude, Sasha keeps the skill's result.

Who can reach it

  • In Sasha, each person sees only the projects they can reach. Their role decides what they can do. See Who can do what in Sasha. Admin and staff accounts can reach every project, members' homes included. A member's home is private from other members, but not from admin and staff. See How Sasha organises your knowledge into projects and documents.
  • From Claude, Claude reaches your knowledge only through a connection that you approve when you connect. A connection never has more access than you have in Sasha. See Connect Claude to your Sasha.
  • You can remove a connection at any time. Remove the connector in Claude. An admin or staff account can also remove Claude in Sasha under Settings, then Connections. Members cannot open Settings, so a member removes the connector in Claude. To stop a member's access for certain, an admin changes the member's grants or deletes the account.

Questions

Is my Sasha shared with other organisations?

No. Each organisation has its own Sasha instance. No other organisation shares it.

Where does our instance run?

Either in your organisation's own cloud account, or Context is Everything hosts it for you. Ask your Sasha administrator which applies to your organisation.

Does Sasha keep my conversations in Claude?

No. Sasha does not receive your conversation. Sasha keeps a log of the requests that Claude makes to Sasha through your connection. The log does not hold Sasha's answers.

How do I stop Claude from reaching Sasha?

Remove the connector in Claude. An admin or staff account can also remove Claude in Sasha under Settings, then Connections. Members cannot open Settings, so a member removes the connector in Claude. To stop a member's access for certain, an admin changes the member's grants or deletes the account.

made with bernard

Cookie settings