> 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-settings/general.md).

# General

<figure><img src="/files/ISuhBrnm6VbwOp6yOGaf" alt=""><figcaption></figcaption></figure>

The **General** settings section allows workspace admins to configure the foundational elements of the workspace. These settings help customize the workspace to fit the identity and needs of the organization.

### General Settings

1. **Workspace Name**
   * The name of the workspace helps identify it among other workspaces you may have access to. This is usually the name of the organization or the project the workspace represents.
   * To change the workspace name, simply enter the new name in the designated field and click **Save**.
2. **Workspace Icon**
   * Customize your workspace by uploading a unique icon or logo. This helps team members quickly identify the workspace, especially if they are part of multiple workspaces.
   * Click on **Upload Image** and select the desired icon from your device.
3. **Workspace URL Slug**
   * The workspace URL slug is a unique identifier for your workspace. It forms part of the URL that team members will use to access the workspace.
   * For example, if your workspace is called “ABC NonProfit,” the URL might look like `team.chat.ngo/abc-nonprofit`. You can edit this slug in the General Settings and click **Save** to confirm changes.

### Additional Settings

1. **Public Chats**
   * Enable or disable public chats in the workspace. Public chats allow users to share chats with people outside of the workspace.&#x20;
2. **Personal Chats**&#x20;
   * Manage the ability for team members to create  private chats that are only visible to them.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.chat.ngo/workspaces/workspace-settings/general.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.