Deploy Cassis to your team
Start with a few colleagues and one business use case. Help them get useful answers, learn from their questions, then extend coverage and access.
Choose the group and questions
Pick colleagues who share a business use case and a few questions they need answered regularly. Check those answers against a trusted query or report. If the questions need more definitions or tables, expand the context to cover them.
Decide how people will get answers
For data questions, a DDL project returns SQL, not executed results. Connecting an assistant to Cassis does not give it warehouse access.
- For results directly in Cassis Chat, a connected assistant or Slack, connect a warehouse to Cassis.
- To keep execution on your side, run the SQL with your own tools. An assistant needs its own warehouse access; otherwise, a person runs the SQL in their SQL editor.
Try the complete flow with the tools and access your colleagues will use. Make clear whether they should expect a result or SQL to run.
Give people access
Have an admin invite your first colleagues as Explorers. They can ask in the Cassis web app’s Chat or connect their usual assistant.
Share the project, a few checked questions and what the context covers. Ask people to answer clarifications and explain mistakes in the same conversation. Have a colleague try a question from their own account and check the answer together.
If colleagues sign in before being invited
Someone without a Cassis account who signs in from an MCP client gets a demo organization of their own. If your organization has claimed their email domain, they wait for an admin to approve them instead. A company MCP gateway adds people from your claimed domains as Explorers on their first question.
Maintain the context together
Give maintainers Editor access and agree who reviews feedback and approves business definitions. Review the chats with Cassis and the gaps it finds, then check and publish the changes. Save approved answers as eval cases to check after later edits.
For Git-managed context, put the files in a shared repository and configure publishing. Maintainers can review changes through pull requests; people asking questions do not need repository access. For app-managed context, use the review and publication workflow in Cassis.
Roll out more widely
Once the first group can get useful answers, widen access through company assistants or an MCP gateway or Slack. Check the next group’s questions and add the coverage they need. Give each business area someone responsible for its definitions and feedback.
Admins can follow usage in Settings → Analytics and inspect conversations needing attention in Settings → Conversations.