> For the complete documentation index, see [llms.txt](https://docs.sola.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sola.security/workspace/chats.md).

# Chats

Ask questions across your entire workspace in private chats

Chats give admins a private, workspace-level chat to ask questions across all connected data sources.

They work just like a project, with every data source in your workspace connected.

**Key differences between Chats and projects**\
Chats and [projects](https://docs.sola.security/workspace/projects.md) share the same building blocks, but differ in a few important ways:

* **Who can use it**: Chats are available to workspace admins and owners only. Projects can include any workspace member.
* **Data access**: Chats connect to every data source in your workspace. Projects connect only to the data sources assigned to them.
* **Visibility**: Chats are private to the admin who created them. Projects are visible to all their members.
* **Collaboration**: Chats are for individual use and cannot be shared. Projects are built for team collaboration, with shared workspaces, member roles, and permissions.

## Using Chats

Chats appear in the sidebar, with your most recent ones listed there for quick access. Click **Chats** to view your full list, or **New Chat** to start a fresh one.

<figure><img src="https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2Fur4RDjdMzLKFwNqU7hgq%2Fworkspace-level%20chat.png?alt=media&amp;token=048b3d10-0f60-4b4d-bebc-e5e5ec2dbf40" alt="Workspace level chats"><figcaption><p>Workspace level chats</p></figcaption></figure>

Inside a chat, ask questions in natural language across every connected data source in your workspace. You can ask questions that span your entire environment without switching between projects.

As you investigate, create queries, canvases, alerts, and workflows directly from the conversation. All assets are owned by that chat.

Your chats are persistent. Return to any previous chat from the sidebar and pick up where you left off.

## Sending emails from chat

Ask Sola to send an email to a teammate or a team inbox. Emails can include findings, reports, and summaries. Sola asks for approval before sending, and sends only to addresses typed in the conversation.

For example: `"How many storage buckets do we have open publicly? Send the results to secops@example.com by email, and include a CSV with the full list."`

* **Where email works:** Email is available in chats, [projects](https://docs.sola.security/workspace/projects.md), and [agents](https://docs.sola.security/workspace/agents.md), including agents that run on a [routine](https://docs.sola.security/workspace/routines.md) or through [Sola MCP](https://docs.sola.security/getting-started/sola-ai/sola-mcp.md). Email is enabled by default. For an agent, Email can be turned off on the Agents configuration page.
* **Attachments:** An email can include CSV, JSON, and NDJSON files. An email sent from a chat can include up to 3 query exports as CSV attachments.
* **Recipients:** Email is sent only to addresses typed in the conversation. For agents, addresses written in the agent's instructions or the task prompt are also allowed. Addresses found in data, such as query results or data source records, are never used as recipients.
* **Limits:** Each email supports up to 5 recipients, including cc, and up to 10 MB of attachments in total. Each agent run can send up to 5 emails.

<figure><img src="https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2Fbr9lGAqqd862lkzmHc7g%2FEmail%20in%20Chat.png?alt=media&amp;token=610551da-9132-42c2-bb78-368e32e0f261" alt="Asking Sola to email results from a chat"><figcaption><p>Asking Sola to email results from a chat</p></figcaption></figure>

## Moving a chat to a new project

Move a chat into a new project your team can join and collaborate on.

To move a chat, open its three-dot menu, from the chat header or from the sidebar, and select Move to a new project.

{% hint style="info" %}
**Privacy and sharing when moving a chat**

After moving a chat to a new project, the chat conversation stays private to you, just as it always has. Its [queries](https://docs.sola.security/workspace/projects/queries.md), [canvases](https://docs.sola.security/workspace/projects/canvases.md), [alerts](https://docs.sola.security/workspace/projects/alerts.md), and [workflows](https://docs.sola.security/workspace/projects/workflows.md) move into the project and become available to your team.
{% endhint %}

***

## FAQs

### Can I share a chat with another admin?

No. Chats are private to the workspace admin or owner who created them and cannot be shared, even with other admins or owners.

### Can members see my chats?

No. The Chats section is only visible to admins. Members do not see it and their experience in projects is unchanged.

### What happens to assets I create in a chat?

Chat assets (queries, canvases, alerts, and workflows) are owned by that chat and stay with it. You can access them any time by returning to the chat.

### Can I turn a chat into a project?

Yes. Open the chat's three-dot menu and select Move to a new project. It creates a new project with the chat's queries, canvases, alerts, and workflows added, ready for your team to build on, and takes you there.

### Can I move a chat into an existing project?

No. Moving a chat always creates a new project. There's no option to add it to a project that already exists.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sola.security/workspace/chats.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
