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

# Workspace Overview

<figure><img src="https://1559385099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKwSDHUZddn74A8yIZpGR%2Fuploads%2Fle2JpxqPCDMmQoO9OS2s%2FCleanShot%202024-10-09%20at%2006.17.31%402x.png?alt=media&amp;token=d4525ef3-dbe7-4268-b0c9-b261f745ba92" alt=""><figcaption></figcaption></figure>

ChatNGO workspaces are designed to keep your projects, teams, and organizations organized and secure. Each workspace is a private environment where you and your team can collaborate on AI chats, share prompts, and manage workflows.

### What is a Workspace?

A **workspace** in ChatNGO is a dedicated space for a specific organization or team. Workspaces allow users to keep their conversations, images, and custom AI models separate from other teams or organizations they may be a part of.

Each workspace contains:

* **Private and Shared Folders** for organizing chats, files, and prompts.
* **Custom Instructions and Personas** to tailor AI outputs for your team.
* **Permissions and Roles** that manage who has access to different sections within the workspace.
* **AI Model Settings** that determine which AI models are available to your team.

### Key Features of a Workspace

* **Multiple Workspaces**: Users can be a part of multiple workspaces if they collaborate with different nonprofits or collaborative projects.
* **Team Collaboration**: Workspaces enable your team to chat, share prompts, and manage AI models collaboratively.
* **Customized AI Models**: Each workspace can have its own set of AI models, specific to the needs of the team.
* **Secure Environment**: Workspaces keep your data private and accessible only to authorized members of your team.

{% hint style="info" %}
In ChatNGO, users cannot create workspaces directly. Instead, workspaces are set up by the platform administrators, and access is granted by the workspace administrators.&#x20;
{% endhint %}

### Access to Multiple Workspaces

You may have access to multiple workspaces in certain cases:

* **Different Organizations or Roles**: If you are associated with more than one nonprofit, for example, as a volunteer for one and a board member for another, you may be invited to join separate workspaces for each organization.
* **Collaborative Projects**: Sometimes, multiple nonprofits work together on a shared project. In such cases, a dedicated workspace may be created for the project, allowing team members from each organization to collaborate in one space.

In each scenario, workspace admins will invite you, and you can easily switch between your workspaces to manage your work across different organizations or projects.


---

# 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.chat.ngo/workspaces/workspace-overview.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.
